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

Ignore immutable registry errors when source image changed with a flag or configuration #69

Open
R1cc4rd07 opened this issue Mar 4, 2022 · 1 comment

Comments

@R1cc4rd07
Copy link

Hi all,

I've encountered an issue uploading images to my immutable registry.

When the source image gets changed for whatever reason dregsy tries reuploading the image but fails because the image tag already exists and can't be overwritten.

Log message:

The image tag '1.20.12' already exists in the 'xxxxxx/kubectl' repository and cannot be overwritten because the repository is immutable.

I think there should be a configuration/flag available to ignore errors like this and simply drop a warning at the end saying something like:

The source image for <insert repo name> was changed in < tag version >. The image was not uploaded because the target registry is immutable.

But this should not be an error just a warning.
I suggest a new field for the configuration of dregsy tasks something like this:

"tasks": {
  [
    "source": {
      "regsitry": "my-registry.com",
      "auth": "xxxxxxxxx"
    },
    "target": {
      "registry": "my-traget-registry.com",
      "auth": "xxxxxxxxx",
      "immutable": true
    },
    ...
  ]
}

or simply a flag called "ignoreImmutable" or something like this.

Let me know what you think.

@emoshaya
Copy link

We're facing the same issue here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants