Files ownership problem when running internal commands

[thecodingmachine]

Files ownership problem when running internal commands

[moufmouf]

Weird... are you having this issue on Ubuntu or Windows?

[WizMik]

Ubuntu 18.04 !

[WizMik]

Okay, it may happen when executing a STARTUP_COMMAND! Running npm -i as a startup command may be responsable for the ownership change before the container is available.

[moufmouf]

Mmmm... STARTUP_COMMAND is supposed to be executed by the docker user... https://github.com/thecodingmachine/docker-images-php/blob/7.2-v1/utils/docker-entrypoint-as-root.sh#L91 BUT: I found this in the code and I can't remember why.... :) https://github.com/thecodingmachine/docker-images-php/blob/7.2-v1/utils/startup_commands.php#L17-L20 Do you happen to have an environment variable named UID with UID=0? Le jeu. 31 mai 2018 à 16:00, WizMik <[email protected]> a écrit :

…

Okay, it may happen when executing a STARTUP_COMMAND! Running npm -i as a startup command may be responsable for the ownership change before the container is available. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#40 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABOyyIujdtS3gWarR-vPKAvWZVxSrMgHks5t3_dsgaJpZM4UTinI> .

[stuchl4n3k]

Hi! I think I experienced a similar issue. By extend your image and just changing WORKDIR the black magic is sadly defeated. Reproduce:

1. Create ./Dockerfile with:

FROM thecodingmachine/php:7.4-v3-slim-apache
WORKDIR /srv

2. Build: docker build -t tcm-test/php .
3. Run: docker run --rm -eSTARTUP_COMMAND_1=id -it tcm-test/php id

uid=0(root) gid=0(root) groups=0(root)
uid=0(root) gid=0(root) groups=0(root)

I guess that /srv is just not supported, right?