You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I usually use the tmpfs command for the /tmp directory (and in this case, I'm using tmp for the backblaze temp storage drive too) to minimize disk writes, using the option:
Hello!
Please try to set USER_ID and GROUP_ID in your docker run command, this user will then be handed over th thoe Backblaze app. You can also create a new user just for Backblze on your system, but note that it needs read-write permissions on the config folder where it stores the install files and logs (that is in your case tmpfs) and also read-write permissions for the shared folders you want to back up (because it creates a .bzvol folder where it stores information to identify the "drive" and also files to check its on/offline state).
Hope that helps!
I usually use the tmpfs command for the /tmp directory (and in this case, I'm using tmp for the backblaze temp storage drive too) to minimize disk writes, using the option:
--mount type=tmpfs,destination=/tmp,tmpfs-size=2000000000,tmpfs-mode=1777
This used to work fine, but it seems sometime in the last month or so it broke. Now I get this error in logs during container startup:
[cont-init ] 85-take-config-ownership.sh: executing...
[cont-init ] 85-take-config-ownership.sh: find: ‘/tmp/tmp.aKbpXZjVMB’: Permission denied
[cont-init ] 85-take-config-ownership.sh: terminated with error 1.
Removing the tmpfs option allows the container to start as expected
The text was updated successfully, but these errors were encountered: