Inside a repository, the image list is currently a flat list of images with and without a tag, respectively. This works fine for single-architecture images like we build ourselves, but now that we've started mirroring images from Docker Hub, we're also dealing with multi-architecture images (which are basically just lists of references to single-architecture images).
What happens right now is that the multiarch image is shown in the list of tagged images, and every constituent singlearch image appears in the list of untagged images. This is obviously dumb because there is no way for the user to understand which multiarch image those images belong to. We should have some sort of visual grouping of singlearch images into their respective multiarch image.
When this is tackled in Elektra, there will need to be some new API in Keppel to deliver the required metadata. Get in touch with me so we can do some design thinking or whatever it's called these days.
majewsky
commented
1 month ago
Inside a repository, the image list is currently a flat list of images with and without a tag, respectively. This works fine for single-architecture images like we build ourselves, but now that we've started mirroring images from Docker Hub, we're also dealing with multi-architecture images (which are basically just lists of references to single-architecture images).
What happens right now is that the multiarch image is shown in the list of tagged images, and every constituent singlearch image appears in the list of untagged images. This is obviously dumb because there is no way for the user to understand which multiarch image those images belong to. We should have some sort of visual grouping of singlearch images into their respective multiarch image.
When this is tackled in Elektra, there will need to be some new API in Keppel to deliver the required metadata. Get in touch with me so we can do some design thinking or whatever it's called these days.