Handle multi-arch Docker images on GitHub Package Registry

I would love for GitHub Package Registry to handle multi-arch Docker images like DockerHub or GCR! :heart:

I have tried through GitHub Actions but failed with the famous 406 Not Acceptable.
As you can see this is okay while pushing to docker.io as logs stipulated (marked done at the end). In fact buildx can’t push the following tags/manifests on docker.pkg.github.com and failed with this 406 error.

This issue occurs because the GitHub Package Registry cannot handle Manifest v2 schema 2.
If you can add this implementation that would be awesome!! :pray:

21 Likes

This also appears to prevent being able to store from cache manifests from Docker BuildKit (which could be an ideal way to add caching to docker image builds in GHA).

7 Likes

Hey @crazy-max,

Thanks for the feedback! I’ve taken your suggestion and passed it along to the appropriate teams. Thanks again for reaching out :grinning:

2 Likes

Can’t wait to see this implemented :fire::boom:

@andreagriffiths11 can you please append this information to https://help.github.com/en/articles/configuring-docker-for-use-with-github-package-registry ? 

Or make a note somewhere that you do not currently support Docker Registry Manifests?

Most image creators Multi Arch now, this is not a corner case functionality and the Docker client automatically pulling the correct image for the users arch is extremely useful.  

4 Likes

Any ETA for this feature? Really need it since the early disruption on Docker Hub :smirk:

4 Likes

I would also love to see this feature implemented.

GitHub Actions are significantly more efficient that DockerHub autobuild, I would like to migrate my all build processes from DockerHub to GitHub, along with GitHub package registry, but the multi-arch feature is blocking for me.

Regards,

Edouard

2 Likes

@andreagriffiths11 I’m getting errors pushing my multi-arch docker image to the GitHub registry and have only just found this thread to see it’s not supported - would be great if the docs could include this somewhere :smiley:

Also, is there an ETA or Issue raised that I can follow anywhere?