builder.yml: Ensure consistent subuid and subgid across builders #2511
+53
−2
Conversation
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
This might explain a lot of the storage weirdness we've been observing. If a container image layer is create in rootless on podman on one machine, that image layer is restored to another host with *different* subuid or subgid, errors can occur. Signed-off-by: David Galloway <david.galloway@ibm.com>
`chown`ing the podman storage directory is problematic when using rootless podman Signed-off-by: David Galloway <david.galloway@ibm.com>
Member
|
mentioned in slack, but adding here for completeness: It seems to be the case that "container images" (like you'd push) do not contain any info about the subuid/subgid mapping used to create them; they have container-internal UIDs in them that will get mapped when instantiated into a container. Do you remember what it was that broke exactly? |
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.
This might explain a lot of the storage weirdness we've been observing. If a container image layer is create in rootless on podman on one machine, that image layer is restored to another host with different subuid or subgid, errors can occur.