[RFE] Support manifests list (Docker & OCI) #107
Comments
runcom
added
kind/feature
|
@runcom is this likely to happen soon? or is https://github.com/estesp/manifest-tool the way to go? |
|
@SvenDowideit I'd love estesp's tool merged back here (where it was forked from, skopeo). I have this on my todo but if anyone wants to take it and help, please do so, I don't have any ETA otherwise. |
|
I too think this would be good to get these tools merged back. @estesp What do you think? |
|
Note that docker upstream is basically merging Phil's tool in the Docker cli (via a subcommand called "manifest"). |
|
FWIW containers/image, and skopeo, can consume docker schema2 manifest lists (by choosing the current architecture). That’s by no means a comprehensive support, of course — but it would be nice to flesh out what this ticket means, “support manifest lists” is too vague to ever say “yes, this has happened”. |
|
It would be great if This probably depends on the destination registry being used. Some implementations may not support manifest lists (quay.io at time of writing). It may also only make sense when the destination is a registry, e.g. |
|
There is a WIP PR at containers/image#400 , I’m afraid the progress has stalled for some time. |
|
Still open issue, though no one is working on it right now, have to gauge priority. |
…mage. Currently the image digest exporter does not implemented the behavior described in the resources doc, which says "if there are multiple versions of the image, the latest will be used." Instead, it reports the digest of `index.json`, which is an image index. This behavior introduces a usability issue: one of the major public container registry --- dockerhub --- does not support OCI image indices, and there are very few tools (if any) that support converting OCI image indices to docker manifest lists. Skopeo currently only support pushing an OCI image index that contain only one image. If the index has more than one images, it requires the user to specify one: containers/skopeo#107 containers/image#400 Essentially, these limitations make the image digest exporter useless. To make this feature useful, the exporter could instead implement the following behavior: 1. If there is only one image in `index.json`, report the image's digest. 2. If there are multiple images, report the digest of the full index. The advantage of this behavior is that, we can immediately use it (in conjunction of GoogleContainerTools/kaniko#744), yet if multi-image manifests are more widely supported, the image digest exporter can still support that without any modification.
…ne image. Currently the image digest exporter does not implemented the behavior described in the resources doc, which says "if there are multiple versions of the image, the latest will be used." Instead, it reports the digest of `index.json`, which is an image index. This behavior introduces a usability issue: one of the major public container registry --- dockerhub --- does not support OCI image indices, and there are very few tools (if any) that support converting OCI image indices to docker manifest lists. Skopeo currently only support pushing an OCI image index that contain only one image. If the index has more than one images, it requires the user to specify one: containers/skopeo#107 containers/image#400 Essentially, these limitations make the image digest exporter useless. To make this feature useful, the exporter could instead implement the following behavior: 1. If there is only one image in `index.json`, report the image's digest. 2. If there are multiple images, report the digest of the full index. The advantage of this behavior is that, we can immediately use it (in conjunction of GoogleContainerTools/kaniko#744), yet if multi-image manifests are more widely supported, the image digest exporter can still support that without any modification.
…ne image. Currently the image digest exporter does not implemented the behavior described in the resources doc, which says "if there are multiple versions of the image, the latest will be used." Instead, it reports the digest of `index.json`, which is an image index. This behavior introduces a usability issue: one of the major public container registry --- dockerhub --- does not support OCI image indices, and there are very few tools (if any) that support converting OCI image indices to docker manifest lists. Skopeo currently only support pushing an OCI image index that contain only one image. If the index has more than one images, it requires the user to specify one: containers/skopeo#107 containers/image#400 Essentially, these limitations make the image digest exporter useless. To make this feature useful, the exporter could instead implement the following behavior: 1. If there is only one image in `index.json`, report the image's digest. 2. If there are multiple images, report the digest of the full index. The advantage of this behavior is that, we can immediately use it (in conjunction of GoogleContainerTools/kaniko#744), yet if multi-image manifests are more widely supported, the image digest exporter can still support that without any modification.
|
Skopeo has |
No description provided.
The text was updated successfully, but these errors were encountered: