Missing perms in doc's

[cyberlink1]

Big plus for actually running the app inside the container as a user and not root!

However, you should include in the docs that the permissions on the /backup directory need to be UID: 1005 GID:1005 for the container to be able to write to it.

Im running it in a swarm so im mounting /backup from an NFS share and, well, lets just say it took me a bit to figure out why it was not producing backups. lol

[deitch]

Big plus for actually running the app inside the container as a user and not root!

Amen, and thanks. I have been in docker for a long time (brought them into a consulting client of mine when they were version zero-point-something), so I appreciate the headache. Then it gets really strange when you are doing it on a Docker Desktop (like macOS or Windows) and the mounts are handled in different ways (older vpnkit).

Based on what you wrote, I would guess that you are running it on Linux directly. It would be great if it could support NFS targets directly, like it does smb+file+s3, but it is not so easy to do.

As an aside, I find it so interesting how people still use it heavily in a container. The entire contents of the container is a single statically-compiled binary, so you can run it just as easily as the executable (and it is on the GitHub releases page).

Do you feel like opening a PR to add it to the docs? It is mostly covered here, anyways, so just add what you think is missing to make it clear.