docker buildx plugin

[Geert Stappers]

Hello,

On a Bookworm system results `DOCKER_BUILDKIT=1 docker build .` in
a succesfull build.

On an unstable system results `DOCKER_BUILDKIT=1 docker build .` in
this output:
|ERROR: BuildKit is enabled but the buildx componet is missing or broken.
| Install the buildx component to build images with BuildKit:
| https://docs.docker.com/go/builds

That webpage says: "Buildx and BuildKit are both installed with Docker
Desktop and Docker Engine out-of-the-box." It explains why the build
works on the Bookworm system. And says it should work on the unstable
system. But here we are ...


My websearch suggested there is package 'docker-buildx-plugin' and
package 'docker-buildx'. "apt" can't find them.


What should be done to get the buildx component working?



Background information:
The Bookworm system:
|$ dpkg -l docker\* | grep ^ii | cut -b -60
|ii docker-compose 1.29.2-3 all
|ii docker.io 20.10.24+dfsg1-1+b3 amd64
|$ docker --version
|Docker version 20.10.24+dfsg1, build 297e128
|$


On the unstable system:
|$ dpkg -l docker\* | grep ^ii | cut -b -60
|ii docker-cli 26.1.5+dfsg1-2+b1 amd64
|ii docker-compose 1.29.2-6 all
|ii docker.io 26.1.5+dfsg1-2+b1 amd64
|$ docker --version
|Docker version 26.1.5+dfsg1, build a72d7cd
|$



Groeten
Geert Stappers

[Geert Stappers]

Post by Geert Stappers
Hello,
On a Bookworm system results `DOCKER_BUILDKIT=1 docker build .` in
a succesfull build.
On an unstable system results `DOCKER_BUILDKIT=1 docker build .` in
|ERROR: BuildKit is enabled but the buildx componet is missing or broken.
| https://docs.docker.com/go/builds
That webpage says: "Buildx and BuildKit are both installed with Docker
Desktop and Docker Engine out-of-the-box." It explains why the build
works on the Bookworm system. And says it should work on the unstable
system. But here we are ...
My websearch suggested there is package 'docker-buildx-plugin' and
package 'docker-buildx'. "apt" can't find them.
What should be done to get the buildx component working?

Knowing that `DOCKER_BUILDKIT=1 docker build .` works
on your Debian unstable system would help. It tells that
the problem is on my side.

Post by Geert Stappers
|$ dpkg -l docker\* | grep ^ii | cut -b -60
|ii docker-compose 1.29.2-3 all
|ii docker.io 20.10.24+dfsg1-1+b3 amd64
|$ docker --version
|Docker version 20.10.24+dfsg1, build 297e128
|$

The Bookworm machine was installed on a new computer,
it was always a Bookworm system.

Post by Geert Stappers
|$ dpkg -l docker\* | grep ^ii | cut -b -60
|ii docker-cli 26.1.5+dfsg1-2+b1 amd64
|ii docker-compose 1.29.2-6 all
|ii docker.io 26.1.5+dfsg1-2+b1 amd64
|$ docker --version
|Docker version 26.1.5+dfsg1, build a72d7cd
|$

That system start as a Stretch system and at some point in time
upgrade to unstable.

What is more likely causing the
|ERROR: BuildKit is enabled but the buildx componet is missing or broken.
the many upgrades or being an unstable system?


Groeten
Geert Stappers

[Jonathan Dowland]

Post by Geert Stappers
My websearch suggested there is package 'docker-buildx-plugin' and
package 'docker-buildx'. "apt" can't find them.

I speculate that the buildx component was formerly part of the upstream
project that is consumed by Debian's docker.io package (in the bookworm
era) and was later split out into a separate upstream project, that is
not (yet) packaged in Debian.

A quick search didn't turn up any Debian bugs for 'buildx' in the Debian
BTS for package: docker.io. If the functionality is broken > bookworm,
it would be worth filing a bug.

Docker-dot-com have their own distinct Docker packages, and their own
APT repository. The package 'docker-buildx-plugin' might exist in that.

Post by Geert Stappers
What should be done to get the buildx component working?

You could try switching from Debian's package of Docker to
Docker-dot-com's:

https://docs.docker.com/engine/install/debian/

I can't vouch for it and I'd suggest considering the advice at
<https://wiki.debian.org/DontBreakDebian> before adding another
APT repository to your system.

You could also take a look at Podman (a largely drop-in alternative
for Docker, also packaged) and see if it has the features you need.