Closed isumix closed 4 months ago
This isn't a bug. The container expects to have control over the /config
and set it to the PUID/PGID provided otherwise it sets to 911 for both.
/config
is the container's folder and the container manages its permissions./config/workspace
is where the container expects the project files and that folder is excluded from permission fixing/config
folder, not some random subfolder to it
Is there an existing issue for this?
Current Behavior
Currently shown in the example to mount into container's
/config
But this willchown -R
anything mountend into this directory with thePUID:PGID
Expected Behavior
Either rewrite docs (README) recommending other location and warning about this behavior. Or fix this behavior. Mounted files` permissions must not be changed.
Steps To Reproduce
As a normal user (not root), run the command below, mounted folder will be chown-ed
Environment
CPU architecture
x86-64
Docker creation
Container logs