fix(cli): start secrets selinux - #6000
Open
7ttp wants to merge 2 commits into
Open
Conversation
7ttp
force-pushed
the
fix/selinux-start-secret-bind
branch
from
July 30, 2026 08:58
1675440 to
8e78fb5
Compare
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
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.
TL;DR
fixes
supabase startfailing withEACCES on SELinux-enforcing hosts(Fedora + rootless Podman)containers couldn't read the CLI-staged files under
supabase/.temp/start-secrets/(Postgres's
pgsodium_root.keyfirst, then Kong/Supavisor secrets and edge-runtime artifacts)It was happening because of the missing SELinux relabel on those bind mounts,
the files keep the workspace label, which a confined container can't read despite the file mode.
So I've introduced a
Zmount option for the three bind sites, which fixes it up:each file gets a private per-container label, sibling containers still can't read them, and user project sources are never touched.
No-op without SELinux, and Docker/Podman both ignore ENOTSUP from non-labelable filesystems, so nothing currently working changes...
refs
Follow-up to fix(cli): pg-delta selinux bind mount #5990