-
-
Notifications
You must be signed in to change notification settings - Fork 322
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
Can't see all architectures associated with a tag #130
Comments
Hi @bjj and thank you for using my project and your issue 👍. First of all, be careful, you are using an experimental docker feature and docker engine and docker registry servers do not evolve synchronously. When you create a multi-arch image, here is what's going on:
{"name":"image-name","tags":["latest"]}
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"schemaVersion": 2,
"config": {
"mediaType": "application/vnd.docker.container.image.v1+json",
"digest": "sha256:13fed3dd0c000a1606eb29eafd20ac3e71751a09469a4c747b3cc6ea2e688414",
"size": 6147
},
"layers": [ "more stuff here" ]
} As you can see, the digest is
{
"architecture": "amd64",
...
} While doing my research (and writing this), I saw that it is possible to get the list of architectures via the manifest list (in my example it was The idea here is to do the This functionality may require major changes to the interface. It could take a long time, but it is still possible. I would probably need your feedback when I start this feature, will it be possible? |
Thanks for the detailed analysis. I'm very new to docker, so I learned a lot.
I think this must be the difference. If I execute As far as I can tell, this is controlled by the
|
Oh yes! Your are right, The drawbacks with the header list is that I'm losing the layers key from the response... I use this to build the size of the Image. But I can do one request per architecture with the digest from the list. (The size in the manifest list is not the size of the image). The docker client header list is
Okay, now I have to think about the new interface to include this 🤔 |
If the list of architectures was in the history page, would you like it? |
Could the list of architectures be "tabs" at the top that let you select what you're looking at? |
tabs at the top of the tag history ? Yes absolutely ! |
Just installed the UI. It was super easy with the REGISTRY_URL once I understood what it meant. The ability to put the registry on a private network and have the UI proxy /v2/ so it's all nice and tidy is fantastic.
Bug description
I'm building multi-platform images using
docker buildx
like this:That is an all-in-one build/tag/push operation that results in an image I can run on arm64 or Raspberry Pi.
The UI shows the image and the (only) tag ("latest"). If I click history I see the amd64 version. Is there some way to see the arm/v7 version as well?
How to Reproduce
Use buildx as described to make a multi-platform image, then inspect with UI.
Expected behavior
Some indication that multiple architectures are supported by the tag. Some way to navigate them?
System information
The text was updated successfully, but these errors were encountered: