Does the daemonless command support parallel build?

[svenikea]

Hi, this may be a dumb question. We have Kubernetes GitLab runners that recently migrated from Docker‑in‑Docker to BuildKit because we couldn’t run Docker build jobs in parallel. However, the issue is the same with both Docker‑in‑Docker and BuildKit:

could not connect to unix:///run/buildkit/buildkitd.sock after 10 trials
========== log ==========
buildkitd: could not lock /var/lib/buildkit/buildkitd.lock: another instance is running?

I’m wondering if it’s possible to run BuildKit on a socket that includes the job ID, so each job gets its own unique socket like this?

buildctl-daemonless.sh build \
  --frontend dockerfile.v0 \
  --local context=. \
  --local dockerfile=. \
  --addr unix:///run/buildkit/$CI_JOB_ID/buildkitd.sock

There's also issue if multiple projects decided to run simultaneously it will just fails

[AkihiroSuda]

For parallel builds you have to run a daemon and then run clients in parallel

[svenikea]

I decided to run the socket as a daemon instead, this allow me to build it in parallel