fix(cli): pg-delta selinux bind mount - #5990
Merged
Merged
Conversation
Coly010
approved these changes
Jul 29, 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.
TL;DR
On SELinux-enforcing hosts (Fedora + rootless Podman),
db pull's pg-delta helper container fails withEACCESreading the CA bundle the CLI writes undersupabase/.temp/pgdelta/. Start it with--security-opt label:disable.The container runs confined as
container_twhile the CLI-written cert keeps the workspace label, so SELinux rejects the read even though file permissions are fine. Disabling label separation is whatdb testalready does for its pg_prove container — it relabels nothing on the host, is a no-op without SELinux, and Bitbucket(which rejects
--security-opt) already gets it cleared by the global filter....With this,
db pullcompletes on SELinux hosts with the default diff engine.The
supabase startpgsodium failure from the same issue has a different root cause (the staged secret bind mount) and will be handled in a follow-up...ref