fix: disable label separation when binding socket #3150
Merged
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.
This change ensures that when mounting unix sockets for enabling dind access, security opt
label=disable
is set for the container.Ref: https://docs.podman.io/en/latest/markdown/podman-system-service.1.html#access-the-unix-socket-from-inside-a-container
See-also: supabase/supabase#33603
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
At present when using rootless podman with SELinux enabled,
supbase start
command fails at health check step.Relates-to: #3099
2025-02-15T15:52:11.439823Z ERROR source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::sources::docker_logs: Listing currently running containers failed. error=error trying to connect: Permission denied (os error 13)
What is the new behavior?
When executing
supabase start
using rootless podman with SELinux enabled, the development environment starts correctly.Additional context