backup: minio in Docker with VirtioFS enabled suffers from wrong permissions

[mmatczuk]

With VirtioFS disabled all works fine.

When enabled the --dry-run and the preliminary check works fine but every copy fails.

API: PutObject
Time: Thu Apr 28 2022 11:45:09 GMT+0200 (CEST)
DeploymentID: 67d3483d-db15-40ba-943c-eb4a0e5c3521
RequestID: 16EA0CD1E85A26CA
RemoteHost: 192.168.100.21
UserAgent: Scylla Manager Agent Snapshot
Error: rename /data/.minio.sys/tmp/9d6e1143-0b63-4c57-b396-928166f30789/7083afec-2215-40c2-b866-18bb93e103fe /data/my-b/backup/sst/cluster/e543f089-0c1f-4501-969e-5f6947f4f212/dc/dc2/node/ec97277e-3eaa-4982-b1a9-d03352f42d81/keyspace/system_schema/table/types/5a8b1ca866023f77a0459273d308917a/md-2-big-CompressionInfo.db: permission denied (*os.LinkError)

Backtrace: 
0: cmd/fs-v1-helpers.go:360:cmd.fsRenameFile()
1: cmd/fs-v1.go:1107:cmd.(*FSObjects).putObject()
2: cmd/fs-v1.go:1012:cmd.(*FSObjects).PutObject()
3: cmd/object-handlers.go:1826:cmd.objectAPIHandlers.PutObjectHandler()
4: net/http/server.go:2047:http.HandlerFunc.ServeHTTP()

If after an unsuccessful backup one changes permissions with chmod 0777 -R the next backup is smooth and fast.

Updating Minio does not help.