Skip to content
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

Sync: Add option to keep full name on target when using YAML #1072

Closed
mfriedenhagen opened this issue Oct 13, 2020 · 6 comments · May be fixed by #1100
Closed

Sync: Add option to keep full name on target when using YAML #1072

mfriedenhagen opened this issue Oct 13, 2020 · 6 comments · May be fixed by #1100

Comments

@mfriedenhagen
Copy link

Hello,

  • I know that this was already discussed in sync: AWS ECR => private registry incorrect namespace #898 and especially in Sync: Add option to keep full name on target #854.
  • However, maybe I can add an usecase:
    • We currently use another program to sync images from a 8 registries to our internal one (docker.example.com).
    • To ease the use, all our internal users (and build systems) have configured docker.example.com as registry-mirrors.
    • So when they run docker run --rm -it alpine, they automatically pull this from docker.example.com/library/alpine and same goes for docker run --rm jenkins/jnlp-slave.
    • We did not find any collisions when using the "group" as path.
    • Now I would like to keep all synced images from e.g. registry.hub.docker.com in one YAML file (currently we sync 185 repositories from there).
    • Another feature which only seems to be available in the YAML file is to define images-by-tag-regex.
    • Without the option to keep the full name, I would need to split this into 185 files and commands.
  • So I really would like to see something like --scoped-without-registry as outlined in Sync: Add option to keep full name on target #854.
@github-actions
Copy link

github-actions bot commented Jun 5, 2021

A friendly reminder that this issue had no activity for 30 days.

@art-shutter
Copy link

Can second this issue as needed

@tbrasser
Copy link

Currently I need to create a yaml per group and loop skopeo-sync over those. This would alleviate that need.

@art-shutter
Copy link

@tbrasser
please see the discussion here #1531

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@mtrmac
Copy link
Contributor

mtrmac commented Jun 27, 2022

Closing in favor of #1531 to decrease the number of places collecting ideas about the sync mapping design.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants