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
When running this this image in a rootless Docker setup, the file ownership get changed as soon as the configuration processing is completed.
You can actually observe this behavior by killing the container before the config processing gets completed. All files will have the correct ownership until the processing completes.
When running a rootless container, the root user in the container is the actual user the container runs under.
I could workaround this issue by simply setting the UID variable to literally anything that is not 0, so I am not sure if this check is somewhat redundant 🤔
For reference here is my docker-compose.yml configuration:
When running this this image in a rootless Docker setup, the file ownership get changed as soon as the configuration processing is completed.
You can actually observe this behavior by killing the container before the config processing gets completed. All files will have the correct ownership until the processing completes.
I guess this is caused by the
$UID == 0
check indocker-mc-proxy/scripts/run-bungeecord.sh
Lines 464 to 466 in de6e68e
When running a rootless container, the root user in the container is the actual user the container runs under.
I could workaround this issue by simply setting the
UID
variable to literally anything that is not0
, so I am not sure if this check is somewhat redundant 🤔For reference here is my docker-compose.yml configuration:
Permissions of the
./proxy/data
directory with the workaround:And here are the permissions of the
./proxy/data
directory without setting theUID
workaround:The text was updated successfully, but these errors were encountered: