-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: dial unix /run/buildkit/buildkitd.sock #1570
Comments
FWIW, this fails with buildx Later this month the images should receive an update for Docker Engine to v23, which will ship a newer BuildKit ( |
@polarathene Don't think that's related to my issue. Here it's about a dial error. Not attestations support per se. Looking back at the logs, it seems the builder failed to boot early actually: https://github.com/docker/buildx/actions/runs/4047460673/jobs/6961507308#step:5:123
|
@crazy-max I think I'm seeing something similar. Here are logs from 3 machines running Ubuntu 22.04 with Docker 23.0.5 after just being rebooted. The same happened with Docker 23.0.4 and BuildKit 0.11.5, but I did not have the debug output on docker commands enabled at that time, and the problem mysteriously self-healed the next run a couple of hours later. The logs talk about attestation, but the The log is pasted from a Gitlab build log, so I am not sure if the strange characters come from Gitlab or Docker. First machine (big):
The build works as expected after this. Second machine (small):
As expected, the build fails. I'm not sure why Third machine (small):
|
same here use: https://github.com/argoproj/argo-workflows/blob/master/examples/buildkit-template.yaml
|
We are also facing the same issue here. Do we have any resolution so far? `
ERROR: exit code 1 |
I literally just installed buildkit from homebrew, and hitting this error. What does it mean? $ brew install buildkit
$ buildctl --help
$ buildctl du
error: failed to call diskusage: Unavailable: connection error: desc = "transport: Error while dialing: dial unix /run/buildkit/buildkitd.sock: connect: no such file or directory"
$ buildctl --version
buildctl github.com/moby/buildkit 0.13.2 2e18d709fefdcc2db20853ee241c75b058189d39 |
facin the same issue in mac m2 |
Any solution to this ? |
I solved this error by adding |
if you still getting this error in mac, you can use |
Got a strange issue in our CI: https://github.com/docker/buildx/actions/runs/4047460673/jobs/6961507308#step:6:16
This attestation error does not look to be the issue. Best guess is checking capabilities fails but got an early issue when connecting to BuildKit.
The text was updated successfully, but these errors were encountered: