-
Notifications
You must be signed in to change notification settings - Fork 515
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
“docker buildx bake” not push multiplatform to registry #3070
Comments
Looks like you're using the containerd store on Docker Desktop. I could not repro on my side when pushing to Docker Hub: group "default" {
targets = [
"test-nginx"
]
}
variable "shared_args" {
default = {
REGISTRY="crazymax"
}
}
target "test-nginx" {
#context = "../"
#dockerfile = "./Dockerfiles/test-nginx"
tags = ["${shared_args.REGISTRY}/test-nginx:latest"]
platforms = ["linux/arm64","linux/amd64"]
output = ["type=registry"]
} FROM busybox
RUN echo hello
https://explore.ggcr.dev/?image=crazymax%2Ftest-nginx%3Alatest Also from your logs:
It exports both manifests so don't think there is anything wrong. What registry are you using? Is your image public so we can take a look? |
@crazy-max The problem is related to the remote registry. My company registry is based on "Mirantis Secure Registry v.2.9.7". If I do the same procedure using my personal account on "hub.docker.com" it works. But I don't understand the difference between "docker buildx build" and "docker buildx bake" other than the mode and ease of building many images at once. Does the registry have any specific requirements or compatibility for Bake? https://explore.ggcr.dev/?image=ziobizio81%2Fbizio%3Aart-nginx-latest
|
This seems to be side-effect of #3023 bug if I'm looking at the progress (I don't know where the build vs bake difference comes from though). Update to v0.22.0 and try again. |
Contributing guidelines
I've found a bug and checked that ...
Description
Hi, I’m using docker desktop on Apple Silicon M1.
I’m trying to use Docker Buildx Bake to build images, and they are all multiplatform images (arm64,amd64).
I point out that they use directly “docker buildx build … --platform linux/amd64,linux/arm64” it works without problems and in the registry I find the same image with both architectures available.
I’m starting to use “bake” to exploit its potential, but it seems that it doesn’t push with both architectures, but I find only the first one defined in the list “platforms = [“linux/arm64”,“linux/amd64”]”, now I find the “arm64” architecture, and if I invert them, I find only “amd64”.
Below I report my configuration and the build command.
The build of both architectures is done but only the first one is pushed to the registry.
Expected behaviour
I expected the build to push Image for both architectures like when I do "docker buildx buil --platform=linux/amd64,linux/aarm64"
Actual behaviour
An image is pushed with only 1 architecture, the first one indicated platforms = ["linux/arm64","linux/amd64"]
Buildx version
github.com/docker/buildx v0.21.1-desktop.2 65a04767fd3000fbac3b7120cc6115d518678e33
Docker info
Builders list
Configuration
Build logs
Additional info
No response
The text was updated successfully, but these errors were encountered: