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
We would like to use skopeo for registry syncing, but without support to skipping existing tags in the destination the amount of resulting docker pulls would be too large on a daily basis (our use-case is very simple - daily syncing of images from dockerhub repo to ghcr).
We have tried running it both in dry-run and without and dockerhub rate-limiting is choking it very quickly. Please let me know if there is already an existing work-around!
The text was updated successfully, but these errors were encountered:
The code is already supposed to avoid syncing images that exist on the destination, based on manifest comparison — but that does require reading at least the manifests.
Removing even more accesses would require making an assumption, necessarily by user opt-in, that once a tag exists, it is never moved to a different image. And a single global tag is unlikely to be ideal for that, at least because the practice of having a :latest tag is very widespread; so we would need a more complex option. That’s tracked in #1498 .
We would like to use skopeo for registry syncing, but without support to skipping existing tags in the destination the amount of resulting docker pulls would be too large on a daily basis (our use-case is very simple - daily syncing of images from dockerhub repo to ghcr).
We have tried running it both in dry-run and without and dockerhub rate-limiting is choking it very quickly. Please let me know if there is already an existing work-around!
The text was updated successfully, but these errors were encountered: