Where is buildkitd.toml when running on WSL2?

Open
#2,906 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker
Domain
devops, infrastructure

Research direction

Start by checking how the WSL2-backed Docker environment handles the three paths listed in the issue: the user distro, docker-desktop, and the Windows host. Verify the effective BuildKit configuration with a build that uses max-parallelism; done means documenting the correct location and any required restart or setup steps.

Written by the indexing model from the issue text.

Description

Where does one put buildkitd.toml when trying to reduce max-parallelism on WSL2 backed Docker on Windows?
I tried all more or less obvious locations I could think of:

  • /etc/buildkit/buildkitd.toml inside of my own WSL2 Distro
  • /etc/buildkit/buildkitd.toml inside of the docker-desktop WSL distro
  • C:\ProgramData\buildkitd\buildkitd.toml on the Host

There is also a suspicious /tmp/docker-desktop-root inside of the docker-desktop WSL distro. It has a bunch of other docker config files in its own /etc. But unfortunately it appears to be mounted from some iso image, and is fully read-only.

Now, where do I actually put the file for it to take effect?

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

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.

More from moby/buildkit

All issues in moby/buildkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.