cmd/initContainer: Avoid RPM failures due to unexpected file owners #640
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
|
Build failed.
|
HarryMichal
requested changes
Dec 2, 2020
debarshiray
added a commit
to debarshiray/toolbox
that referenced
this pull request
Dec 2, 2020
When running rootless, files and directories bind mounted from the host operating system can have their ownership listed as nobody:nobody. This is because the UIDs and GIDs that actually own those locations are not available inside the container. Some distribution packages are particular about the file ownerships of some of these locations. eg., Fedora's filesystem RPM. Encountering nobody:nobody as the owner can fail package management transactions involving such packages leading to unforeseen consequences. Therefore, configure RPM to leave these locations alone. containers#640
debarshiray
force-pushed
the
wip/rishi/netsharedpath
branch
from
14afafa
to
4bca04f
Compare
|
Note that this doesn't seem to be working as I thought it would. |
|
Build succeeded.
|
praiskup
reviewed
Dec 15, 2020
HarryMichal
added
2. Container Realm
debarshiray
added a commit
to debarshiray/toolbox
that referenced
this pull request
Nov 17, 2021
When running rootless, files and directories bind mounted from the host operating system can have their ownership listed as nobody:nobody. This is because the UIDs and GIDs that actually own those locations are not available inside the container. Some distribution packages are particular about the file ownerships of some of these locations. eg., Fedora's filesystem and libvirt-libs RPMs. Encountering nobody:nobody as the owner can fail package management transactions involving such packages leading to unforeseen consequences. Therefore, configure RPM to leave these locations alone. containers#640
debarshiray
force-pushed
the
wip/rishi/netsharedpath
branch
from
4bca04f
to
d9ba7ca
Compare
When running rootless, files and directories bind mounted from the host operating system can have their ownership listed as nobody:nobody. This is because the UIDs and GIDs that actually own those locations are not available inside the container. Some distribution packages are particular about the file ownerships of some of these locations. eg., Fedora's filesystem, flatpak and libvirt-libs RPMs. Encountering nobody:nobody as the owner can fail package management transactions involving such packages leading to unforeseen consequences. Therefore, configure RPM to leave these locations alone. containers#640
debarshiray
force-pushed
the
wip/rishi/netsharedpath
branch
from
d9ba7ca
to
7542f5f
Compare
|
This fixes the We might have to tweak the list of paths in |
|
Build failed.
|
|
This is really great news! |
allisonkarlitskaya
added a commit
to allisonkarlitskaya/lisbox
that referenced
this pull request
Dec 10, 2021
allisonkarlitskaya
added a commit
to allisonkarlitskaya/lisbox
that referenced
this pull request
Dec 10, 2021
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.
When running rootless, files and directories bind mounted from the
host operating system can have their ownership listed as
nobody:nobody. This is because the UIDs and GIDs that actually ownthose locations are not available inside the container.
Some distribution packages are particular about the file ownerships of
some of these locations. eg., Fedora's
filesystemRPM. Encounteringnobody:nobodyas the owner can fail package management transactionsinvolving such packages leading to unforeseen consequences.
Therefore, configure RPM to leave these locations alone.