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
Since /bin/dockerfile-frontend does not exist on my localhost, I'm assuming buildx is launching a process in it's own namespaces and attempting to access a file in its own mount namespace.
I'm to assume at first glance that whereever /bin/dockerfile-frontend lands on the host file system, it is not being labeled with the container_t domain and the policy is blocking execution.
The text was updated successfully, but these errors were encountered:
Hello,
I am working on a Fedora 34 machine with moby engine installed.
My work uses buildx to create our containers locally on our workstations.
When SELinux is enabled, building with
buildx
fails.Since
/bin/dockerfile-frontend
does not exist on my localhost, I'm assumingbuildx
is launching a process in it's own namespaces and attempting to access a file in its own mount namespace.I'm to assume at first glance that whereever
/bin/dockerfile-frontend
lands on the host file system, it is not being labeled with thecontainer_t
domain and the policy is blocking execution.The text was updated successfully, but these errors were encountered: