Allow for the container to be run with any UID/GID. Preferably this would use the docker --user flag but alternatively could use an environment variable which is used by the entrypoint. Currently when the user is set the home is set to / and the data directory is then set to /.imap-backup which any non-root user will not have the permission to create.
Need to ensure that the volume is consistent regardless of if it's running as root or another user and ensure that regardless of which user it's being run as that the ~/.imap-backup has permission for that user on first-run. The imap-backup program automatically sets permissions on the ~/.imap-backup directory which should be beneficial.
Allow for the container to be run with any UID/GID. Preferably this would use the docker
--userflag but alternatively could use an environment variable which is used by the entrypoint. Currently when the user is set the home is set to/and the data directory is then set to/.imap-backupwhich any non-root user will not have the permission to create.Need to ensure that the volume is consistent regardless of if it's running as root or another user and ensure that regardless of which user it's being run as that the
~/.imap-backuphas permission for that user on first-run. Theimap-backupprogram automatically sets permissions on the~/.imap-backupdirectory which should be beneficial.