Closed foozmeat closed 11 months ago
I have confirmed that removing the chown line allows the container to startup OK
Same issue with Docker userns-remap feature and PUID=PGID=33 https://docs.docker.com/engine/security/userns-remap/
...
chown: changing ownership of '/config/php': Operation not permitted
chown: changing ownership of '/config': Operation not permitted
[cont-init.d] 40-install: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
...
should now soft-fail if it cannot change perms.
My docker-compose block looks like
When the container boots I run into the following error
and then the container restarts and the loop continues. This seems to be caused by using the VirtioFS driver. See this related issue: https://github.com/causefx/Organizr/issues/1907
If
40-install
simply didn't try and change permissions on /config I think we could avoid this issue. It seems incorrect to usechown -R abc:abc
when we're passing in a preferred UID/GID.