You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have an existing manifestlist (multi-arch) image, like the standard "busybox" image, it would be nice if this was easy to "republish" in its full manifestlist-form via ipdr/IPFS.
If I do a naive docker pull busybox, I only get the image relevant for my local platform. Similarly a naive docker pull busybox && ipdr push (or a combined ipdr push --docker-registry-host index.docker.io busybox) only converts one of the images in the manifestlist.
It would be neat if there was a "manifestlist-aware" process that just did the right thing. Since regular docker pull/push is weak in this area too, I suggest just skipping them and providing a one-stop ipdr migrate busybox (or whatever subcommand) that does all the required pulling+pushing in one go.
The text was updated successfully, but these errors were encountered:
If I have an existing manifestlist (multi-arch) image, like the standard "busybox" image, it would be nice if this was easy to "republish" in its full manifestlist-form via ipdr/IPFS.
If I do a naive
docker pull busybox
, I only get the image relevant for my local platform. Similarly a naivedocker pull busybox && ipdr push
(or a combinedipdr push --docker-registry-host index.docker.io busybox
) only converts one of the images in the manifestlist.It would be neat if there was a "manifestlist-aware" process that just did the right thing. Since regular
docker pull/push
is weak in this area too, I suggest just skipping them and providing a one-stopipdr migrate busybox
(or whatever subcommand) that does all the required pulling+pushing in one go.The text was updated successfully, but these errors were encountered: