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
It seems that GID and UID of the vdirsyncer user were changeable via corresponding parameters e.g. in the docker-compose.yml file but this possibility was removed in version 2.4.1. Since version 2.4.1 GID and UID are fixed to 1000.
This creates files permission problems when using vdirsyncer with local filesystem type storage e.g. on Syology NAS where UID 1000 is not permitted.
Currently, I need to patch the UID and GID in the Dockerfile to the UID/GID of the local Synology user that uses the local filesystem type CALDAV storage.
This could be avoided, if the GID an UID were made settable via parameters in the docker-compose file as it presumably was the case before version 2.4.1. This would be my change request.
BR/Harald
The text was updated successfully, but these errors were encountered:
I did this to drop the root privileges from the container completely, is it possible, that you use docker volumes instead?
With them you don't have the file permission problems.
as said above, II am using vdirsyncer to sync local files on a Synology NAS outside the part of the file system that is managed by docker and owned by a different user than the docker user.
Therefore, I don't see a way how this can by accomplished by using docker volumes.
It seems that GID and UID of the vdirsyncer user were changeable via corresponding parameters e.g. in the docker-compose.yml file but this possibility was removed in version 2.4.1. Since version 2.4.1 GID and UID are fixed to 1000.
This creates files permission problems when using vdirsyncer with local filesystem type storage e.g. on Syology NAS where UID 1000 is not permitted.
Currently, I need to patch the UID and GID in the Dockerfile to the UID/GID of the local Synology user that uses the local filesystem type CALDAV storage.
This could be avoided, if the GID an UID were made settable via parameters in the docker-compose file as it presumably was the case before version 2.4.1. This would be my change request.
BR/Harald
The text was updated successfully, but these errors were encountered: