Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automatically start buildkit for minikube image build for containerd #11195

Closed
afbjorklund opened this issue Apr 25, 2021 · 2 comments · Fixed by #12076
Closed

Automatically start buildkit for minikube image build for containerd #11195

afbjorklund opened this issue Apr 25, 2021 · 2 comments · Fixed by #12076
Assignees
@spowelljr
Labels
co/runtime/containerd kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
1.23.0

Comments

@afbjorklund
Copy link
Collaborator

afbjorklund commented Apr 25, 2021 •
edited
Loading

Trying to build an image for containerd will likely result in an error like:

error: failed to get status: rpc error: code = Unavailable desc = connection error: desc = "transport: error while dialing: dial unix /run/buildkit/buildkitd.sock: connect: no such file or directory"

This is because of the missing packaging and units, for buildkitd component.

The workaround suggested by upstream is to start the daemon up manually:

sudo -b buildkitd --oci-worker=false --containerd-worker=true --containerd-worker-namespace=k8s.io

It is documented when running buildctl, but not for minikube image build

https://minikube.sigs.k8s.io/docs/handbook/pushing/#6-pushing-directly-to-in-cluster-containerd-buildkitd

Eventually it is supposed to be started up with systemd socket-activation.

sudo systemctl start buildkit.socket

#9947

moby/buildkit#1923

But it is not yet available in any released version of BuildKit, such as 0.8.2

#10068

moby/buildkit#1793
@afbjorklund afbjorklund added co/runtime/containerd kind/documentation Categorizes issue or PR as related to documentation. labels Apr 25, 2021
@afbjorklund afbjorklund mentioned this issue May 7, 2021
Closed
@spowelljr spowelljr added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 17, 2021
@sharifelgamal sharifelgamal changed the title Document known build issue with the buildkit socket missing Automatically start buildkit for minikube image build for containerd Jun 14, 2021
@sharifelgamal sharifelgamal added this to the 1.23.0-candidate milestone Jun 14, 2021
@sharifelgamal sharifelgamal self-assigned this Jun 28, 2021
@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Jul 19, 2021 •
edited
Loading

There is a new 0.9.0 release of buildkit out now, which includes the systemd files

https://github.com/moby/buildkit/releases/tag/v0.9.0

@medyagh medyagh assigned spowelljr and unassigned spowelljr and sharifelgamal Jul 20, 2021
@spowelljr
Copy link
Member

In-progress

@spowelljr spowelljr mentioned this issue Jul 21, 2021
Merged
@spowelljr spowelljr added kind/feature Categorizes issue or PR as related to a new feature. and removed kind/documentation Categorizes issue or PR as related to documentation. labels Jul 26, 2021
@spowelljr spowelljr mentioned this issue Jul 29, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spowelljr spowelljr

Labels
co/runtime/containerd kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
1.23.0
Development

Successfully merging a pull request may close this issue.

Auto start buildkit daemon on image build for containerd spowelljr/minikube
3 participants
@afbjorklund @sharifelgamal @spowelljr