-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
No vendor packages available for buildkit installation #10068
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
This got even worse with the systemd units, even more files to download and manually install... https://github.com/moby/buildkit/tree/master/examples/systemd Some input for #11327, that wants to go back to more primitive packaging also for containerd/docker ? The tarballs are only slightly better than downloading "raw" binaries |
/remove-lifecycle rotten |
This is to be expected (long-term), there are no upstream packages for containerd either. |
Unfortunately there are no packages available for "buildkit" yet, only for containerd.
This makes a lot more cumbersome to install and maintain it, using only the tarballs.
Compare:
With:
See moby/buildkit#1794
It would be even better if upstream provided individual deb packages, but beggars can't be choosers...
docker-ce
docker-ce-cli
containerd.io
buildkit
Another general problem with the vendor packages (unlike the system packages) is the lack of source code.
docker.io
containerd
runc
buildkit
But this goes for the other vendor packages, too.
The text was updated successfully, but these errors were encountered: