Rootless does not start on GKE Autopilot
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 48
Description
When trying to run rootless 0.10.5 on GKE Autopilot (using https://github.com/moby/buildkit/blob/master/examples/kubernetes/deployment%2Bservice.rootless.yaml), it fails with:
[rootlesskit:parent] error: failed to setup UID/GID map: newuidmap 10 [0 1000 1 1 100000 65536] failed: newuidmap: Could not set caps
: exit status 1
Even when I run docker run --rm moby/buildkit:v0.10.5-rootless getcap /usr/bin/newuidmap /usr/bin/newgidmap locally I get:
[rootlesskit:parent] error: failed to start the child: fork/exec /proc/self/exe: operation not permitted
When I run getcap /usr/bin/newuidmap /usr/bin/newgidmap in GKE, I get no error message.
So how must this all be configured to run on GKE?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with examples/kubernetes/deployment+service.rootless.yaml and the moby/buildkit:v0.10.5-rootless image configuration. Reproduce the UID/GID mapping and capability errors on GKE Autopilot, then verify the required configuration by running the listed getcap checks and the rootless workload. Done means rootless BuildKit starts successfully on GKE Autopilot without these errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, google-cloud, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100