-
Notifications
You must be signed in to change notification settings - Fork 459
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
Failed to push image: failed commit on ref #1653
Comments
What registry are you using? The response you get:
This looks very strange - getting a 500 response in an internal registry seems like an external problem - I don't suppose you have logs from your registry that you can share? |
The problem is not with my repository. I tried on Gitlab and I have the same problem except that Gitlab gives me a 404 error. When I use |
Out of curiosity, does setting |
Yes ! But why ? |
I suspect it's something to do with an older registry that doesn't support OCI images (the standard that the industry is moving to, instead of docker-specific media types). With BuildKit v0.11, we produce attestations, which automatically require using OCI media types. Asked again - what's the software powering your registry? From your logs I'm guessing harbor? If so, that seems similar to docker/build-push-action#780 (comment), my suggested solution for that was:
Does pushing to GitLab with |
Sorry, the repository is Nexus OSS 3.30.1-01 Note that a few months ago, I was able to push multi-architecture images built with buildx without any problem. |
I have the same problem |
Nexus supports OCI index spec since 3.47.1, see docker/build-push-action#800 and our e2e tests: https://github.com/docker/build-push-action/actions/runs/6453977865/job/17518599615#step:11:393 Like @jedevc said, you can disable provenance if you registry does not support OCI index. |
Work for me , thanks |
Contributing guidelines
I've found a bug and checked that ...
Description
I'm trying to build and upload a docker image to a private repository.
No problem when I export the image locally on my machine.
I have seen several issues of this kind, but none of them solved the problem.
Maybe someone has a list of things to do for this kind of issue ?
Expected behaviour
The image is sent to the repository.
Actual behaviour
I have the following error:
Buildx version
github.com/docker/buildx v0.10.0 8764628
Docker info
No response
Builders list
Configuration
To be sure that the bugs does not come from my Dockerfile, I tested with an example Dockerfile that's comes from https://docs.docker.com/language/python/build-images/
The following command is used:
Logs
Additional info
I have tried the following things (not in order):
docker buildx prune
.docker
directory and restart dockerThe text was updated successfully, but these errors were encountered: