The images are using a docker user, which has 1000 as user and group IDs. This user is the one used to run the FPM and Apache (mod_php) services.
The main purpose of these images is development and testing, with the developed application being bind-mounted in the container. This can cause permission issues if the host user does not have the same ID (1000) than the container.
Some attempts were made (see #227) to change the ID of the user when launching the container, or not to have any user (other than root) in the container and configure at startup the IDs used to run FPM or Apache. But both those approaches had issues.
As this situation is far from being systematic (only on some Linux with custom installers, as 1000 is supposed to be the ID by default most of the time, including the VM used to run Docker on Windows and MacOS), a much simpler solution is to document the usage of lebokus/bindfs docker plugin.
This plugin allows to map the user's ID and group between host and container, solving our issue.
A link to this new documentation will have to be added in the PIM documentation.
The images are using a
dockeruser, which has1000as user and group IDs. This user is the one used to run the FPM and Apache (mod_php) services.The main purpose of these images is development and testing, with the developed application being bind-mounted in the container. This can cause permission issues if the host user does not have the same ID (1000) than the container.
Some attempts were made (see #227) to change the ID of the user when launching the container, or not to have any user (other than root) in the container and configure at startup the IDs used to run FPM or Apache. But both those approaches had issues.
As this situation is far from being systematic (only on some Linux with custom installers, as 1000 is supposed to be the ID by default most of the time, including the VM used to run Docker on Windows and MacOS), a much simpler solution is to document the usage of lebokus/bindfs docker plugin.
This plugin allows to map the user's ID and group between host and container, solving our issue.
A link to this new documentation will have to be added in the PIM documentation.