Fix locate gemfile/6510#6513
Open
Wl0cKk wants to merge 5 commits into
Open
Conversation
On SELinux-enforcing hosts (e.g. Fedora, RHEL) running podman, bind mounts without the "z" label are blocked by SELinux, so the project directory appears empty inside the container and bundler exits with "Could not locate Gemfile". The label is a no-op where SELinux is not enforcing, so this is safe for Docker users.
This was referenced Jul 9, 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
The tested solution of #6510
Based on PR - #6511
6511 is not ready, I ran into some issues while validating PR 6511
All the errors in that PR are shown in the screenshots in comments section.
My Solution is fixing all related issues with building on Fedora with SELinux set to "enforced"
with dependencies and safe.directory (git)
Also satisfy rails version 7.1 -> 7.2
Also -
In projects of this scale,
Gemfile.lockshould be excluded from.gitignoreto prevent future errors; I will be opening an issue regarding this problem shortly.At this moment, no issues, and PR is ready!
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:
The following are not always needed: