Fedora Account System
Red Hat Associate
Red Hat Customer
After upgrading to moby-engine 24.0.5-1.fc38 on Silverblue, unfortunately Buildkit is no longer available while it was working fine on the previous version. For example when running DOCKER_BUILDKIT=1 docker-compose build will present an error message: ERROR: BuildKit is enabled but the buildx component is missing or broken. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/buildx/ Manually installing package golang-github-moby-buildkit did not make a difference. Reproducible: Always Steps to Reproduce: 1.Start a container image build with shell/env variable DOCKER_BUILDKIT=1 Actual Results: ERROR: BuildKit is enabled but the buildx component is missing or broken. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/buildx/ Expected Results: Buildkit working fine, as was the case with the previous version of the moby-engine package.
Also affected by this bug after upgrading to Fedora 38. I need BuildKit, and I can't switch to official packages as I also use Waydroid (wich depends on container-selinux, which causes SELinux errors when trying to start Docker from official packages)
For completeness, a docker build without DOCKER_BUILDKIT gives: DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/buildx/ In other words, in 'a future release' it will no longer be possible to build containers.
ATM we need disable DOCKER_BUILDKIT IIRC I tried , but go lang packaging have a hell of dependencies , I may give up . we need upgrade container to 1.7.x first . fyralabs.com had one solution on https://github.com/terrapkg https://github.com/terrapkg/packages/blob/frawhide/anda/docker/containerd/containerd.spec but I hadn't time yet to test it , basically is build the package with vendor and with go deps
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
A few months ago I was looking for this bug but on buildkit component can you try https://copr.fedorainfracloud.org/coprs/gotmax23/docker-ng/ ? I want build buildkit against it
*** Bug 2242890 has been marked as a duplicate of this bug. ***
(In reply to Youri Westerman from comment #0) > After upgrading to moby-engine 24.0.5-1.fc38 on Silverblue, unfortunately > Buildkit is no longer available while it was working fine on the previous > version. > > For example when running DOCKER_BUILDKIT=1 docker-compose build will present > an error message: > ERROR: BuildKit is enabled but the buildx component is missing or broken. > Install the buildx component to build images with BuildKit: > https://docs.docker.com/go/buildx/ > > Manually installing package golang-github-moby-buildkit did not make a > difference. I will check this soon ... I'm copying this just for the record
buildctl is finally available, for now just on Fedora 42+ dnf install docker-buildkit
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.