fix: add --security-opt label=disable to buildah from (2025.4)#116
Merged
Conversation
Prevents SELinux MCS category mismatch when buildah runs inside a podman container. Without this, the nested buildah container gets different MCS labels than the outer container, blocking access to /etc/resolv.conf and causing DNS resolution failures during image builds. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
atheurer
approved these changes
May 8, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Backport SELinux buildah fix to 2025.4. Fixes DNS resolution failures during engine image builds on systems with SELinux enforcing.
Adds
--security-opt label=disabletobuildah fromto prevent SELinux MCS category mismatch when buildah runs inside a podman container.Test plan
🤖 Generated with Claude Code