RFC: init_buildsystem: Fix create_devs in containers without mknod #1109
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
In rootless podman containers, mknod is not allowed, but bind mounting existing devices is. By bind mounting needed devices, chroot builds can work.
Vogtinator
force-pushed
the
morepodmanbuild
branch
from
00e4927 to
6408a6a
Compare
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.
In rootless podman containers, mknod is not allowed, but bind mounting existing
devices is. By bind mounting needed devices, chroot builds can work.
RFC because: Not sure if I'm missing something. Cleanup doesn't appear to happen, probably because rpmbuild is exec'd at the end, so umount never runs.
Depends on #1108