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
Allow setting of UID and GID used by the container.
By implementing this, when bind mounts are used, users are not forced to allocate the containers fixed UID/GIDs to Onlyoffice on the host system as well.
What is the current behavior?
UID 109 and GID 111 are used by the container and cannot be changed easily.
This makes me wonder, is it practical to allow setting all these IDs to custom values by means of some mechanism (e.g said env variables), or should I just use docker volumes that at least provide some level of UID/GID isolation, given that the files are not accessible by the host directly?
No matter what, I think it would be beneficial to allow mapping all services inside of the container to UIDs and GIDs that are not in use on the host by any other service.
Feature request
Allow setting of UID and GID used by the container.
By implementing this, when bind mounts are used, users are not forced to allocate the containers fixed UID/GIDs to Onlyoffice on the host system as well.
What is the current behavior?
UID 109 and GID 111 are used by the container and cannot be changed easily.
What is the expected behavior?
UID and GID can be set to custom values, e.g. by environment variables PUID and PGID, e.g. as with linuxserver.io images: https://github.com/linuxserver/docker-mariadb?tab=readme-ov-file#docker-compose-recommended-click-here-for-more-info
See also: #40 (comment)
DocumentServer Docker tag:
latest
, but all versions should be affected.Host Operating System:
Ubuntu 22.04 LTS
The text was updated successfully, but these errors were encountered: