moby / moby/buildkit

[buildx] - SELinux policy denied

Open
#2,295 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/security kind/enhancement
Dominant language
Go
Stars
10.3k
Forks
1.5k
Avg merge
1d 23h
Merged PRs (30d)
48

Description

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.

Aug 03 19:33:58 fedora audit[629437]: AVC avc:  denied  { entrypoint } for  pid=629437 comm="runc:[2:INIT]" path="/bin/dockerfile-frontend" dev="nvme0n1p2" ino=260 scontext=system_u:system_r:container_t:s0:c675,c1001 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing a buildx build on Fedora 34 with SELinux enabled and inspect the reported AVC denial for /bin/dockerfile-frontend. The issue is resolved when the build completes without SELinux blocking the frontend process.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go, linux
Domain
build-system, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.