fix(runtime): run php-fpm as remapped user#54
Merged
Conversation
dkh94
force-pushed
the
fix/symfony-env-permissions
branch
from
b6f0e88 to
7226f95
Compare
dkh94
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Relaunch PHP-FPM as the remapped www-data user after the container entrypoint updates UID/GID from PUID/PGID.
Without this, docker exec resolves www-data to the host UID after startup, but the long-running php-fpm master and worker processes can remain on the original image UID 1000. That breaks reads for files owned by the remapped host UID, such as restrictive Symfony .env.local files.
Adds a regression check for the entrypoint behavior.