Makefile: Do not set user ID for container processes when using Podman #8
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
With Podman the container root user is mapped to the user that starts the container. This means the file permissions are already correct and using a different user inside the container results in missing file permissions. Only set the user ID for Docker, not when Podman is used through a "docker" wrapper script.
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.
With Podman the container root user is mapped to the user that starts
the container. This means the file permissions are already correct and
using a different user inside the container results in missing file
permissions.
Only set the user ID for Docker, not when Podman is used through a
"docker" wrapper script.
How to use/testing done
make/make test