-
Notifications
You must be signed in to change notification settings - Fork 58
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
odsComponentStageCopyImage fails for some sourceImageUrlIncludingRegistry strings #1174
Comments
According to the parameter description this is not a bug.
Nevertheless I'd agree that a source format of type |
Following code section builds the given string, derived from the requirement to use A possible solution could be to check if stringA consists of two elements if split by "." (dot). I've created a demo code however I'm not sure if this is intended. |
@tbugfinder thank you for taking care of this so quickly. |
Well, most often I find myself just copy/paste those image strings from the registries. |
Describe the bug
We import images from a private registry. Unfortunately some images are in the following format:
private-registry.com/kong:3.0.1
The component fails in this case because it prepends the internal registry:
skopeo copy --src-tls-verify=false --src-creds user@....:**** docker://image-registry.openshift-image-registry.svc:5000/private-registry.com/kong:3.0.1 --dest-creds
If an image is provided in the following format, the component is successful:
private-registry.com/repo/kong:3.0.1
To Reproduce
Steps to reproduce the behavior:
Use
[REGISTRY/]IMAGE[:TAG]
Expected behavior
Allow
[REGISTRY/]IMAGE[:TAG]
and[REGISTRY/]REPO/IMAGE[:TAG]
Log Output (ensure to remove any confidential information like tokens, project names, etc.
Additional context
#1119
The text was updated successfully, but these errors were encountered: