fix: use UID 1000 for container user to match typical Linux host users#77
Merged
fix: use UID 1000 for container user to match typical Linux host users#77
Conversation
Fixes permission denied errors when mounting volumes. Most Linux desktop users have UID 1000, so bind-mounted directories now work without manual chown. Fixes #76
sgasser
force-pushed
the
fix/container-uid-permissions
branch
from
893b2ca to
295b3fd
Compare
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
1 participant
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.
Summary
Root cause
The Presidio base image uses UID 1001, but most Linux desktop users have UID 1000. When bind-mounting
./data, the host directory is owned by UID 1000, so the container process (UID 1001) couldn't write to it.Test plan
docker compose builddocker compose up -ddocker compose logs pasteguardFixes #76