[docker/podman] Fix user permissions #166
Merged
Conversation
This file contains 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
nasahlpa
force-pushed
the
fix_permissions
branch
3 times, most recently
from
05fc0a6 to
f51cb99
Compare
Before this commit, the container started as root with the following warnings: ` Creating user 'ot' with UID=0, GID=0. groupadd: GID '0' already exists useradd: UID 0 is not unique runuser: user ot does not exist root@ot-sca:/repo# ` With podman 4.3, the option --userns=keep-id when running the container forwards the UID & GID. Hence, no manual permission management is needed anymore. Now, the user inside the container matches the user starting it. Signed-off-by: Pascal Nasahl <[email protected]>
nasahlpa
force-pushed
the
fix_permissions
branch
from
f51cb99 to
0a45aea
Compare
nasahlpa
requested review from
alphan,
andreaskurth,
vogelpi and
vrozic
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Before this commit, the container started as root with the following warnings:
With podman 4.3, the option --userns=keep-id when running the container forwards the UID & GID.
Hence, no manual permission management is needed anymore.
Now, the user inside the container matches the user starting it.