-
Notifications
You must be signed in to change notification settings - Fork 269
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
Make buildx available in official Docker images #322
Comments
Great feedback! We're looking into this. |
In the meantime there is Not official of course... |
Can also use https://hub.docker.com/r/maniator/dind-buildx/ 👍 |
I finally fixed auto builds with GitHub actions, not sure why they stopped.... |
A PR is up to implement this :) docker-library/docker#361 |
This has been merged in docker-library/official-images#12403. Big thanks to everyone involved. ❤️ |
@wedi could you please tell me evenually which official docker image contains buildx now? |
@a-a-k that'd be https://hub.docker.com/_/docker (specifically the |
Tell us about your request
Buildx is the way to go forward and take advantage of the great features BuildKit brought to Docker. buildx is available on every (most?) platforms by default when you install docker with one notable – and somewhat ironic – exception: the official Docker images. The official Docker images seem to be the only distribution packages that do not ship with buildx (and compose) by default. Let that sink in.
That is strange in itself, but it's a real bummer when you start to transition to buildx locally because it's seemingly available everywhere by default and prepare to move on to CI. All shiny new workflows are broken and you need to revert back to regular builds. Not only does this hinder the adoption of buildx (and composer), this burns countless developer hours, judging by the number of people who reacted on the related issues.
Which service(s) is this request for?
Official Docker images on Docker Hub, especially the Docker-in-Docker variants ( tagged dind).
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I would like to use buildx in CI without a hassle. At the moment, this requires me (and everyone who wants to use buildx in a Docker-in-Docker CI workflow) to build and maintain a variant of the official Docker images from Docker Hub – or give up on the advantage of using an official image and rely on a friendly guy from the internet.
Are you currently working around the issue?
Yes, I have created and regularly check and update a custom version of the official Docker images.
Additional context
The first trace of this request dates back to 2019 and there have been multiple duplicates.
There is a more than two years old pull request to resolve the current blocker and a member of the Docker team provides an image as a "temporary" workaround since December 2020 with 100K+ pulls.
I have already asked to reconsider this a few weeks ago and stumbled over this roadmap repo today.
You added buildx support to GitHub actions in fall 2020. It would be very kind if you could add buildx to the official Docker images in spring 2022.
The text was updated successfully, but these errors were encountered: