You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SELinux labelling does not get disabled when using Podman machines #1347
Since #1045, SELinux labelling is supposed to get disabled for devcontainers when using Podman. However, this only works when Podman runs directly on the same (Linux) host as the devcontainers CLI. It is never applied with a Podman machine (the default on macOS and Windows) and the decision is made on the wrong host when Podman is remote (e.g. through an SSH tunnel) or a Podman machine runs on Linux.
Consider the current code of isUsingSELinuxLabels() for image builds. Container run args have a similar issue in getPodmanArgs().
Neither will cliHost.platform always be "linux", nor will running getenforce on the local host always yield the right result. On macOS, getenforce doesn't exist, so the call throws and returns false.
The correct way would probably be to always use podman info and remove the preceding checks.
Hi, I’d like to take this on. I’d trace the build and run argument paths, use Podman’s reported host security state where appropriate, and cover local Linux, Podman machines and remote connections. Is podman info the preferred source for both paths, with graceful fallback when the field is unavailable?
Activity
darshpatel1052 commentedon Nov 3, 2026
Hi, I’d like to take this on. I’d trace the build and run argument paths, use Podman’s reported host security state where appropriate, and cover local Linux, Podman machines and remote connections. Is podman info the preferred source for both paths, with graceful fallback when the field is unavailable?