-
Notifications
You must be signed in to change notification settings - Fork 788
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
Image Paths are not evaluated correctly when attempting a skopeo sync to another GitLab Instance #2461
Comments
Thanks for reaching out. AFAICS this works as expected: see the documentation of If you want to report that you see an error message, please include that error message (or, in general, steps to reproduce / actual results / expected results). |
Hey, thanks for the response. I don't want to keep the registry name because the domain of the registry is different, but the group structure is the same. Also, I cannot include the logs due to being in an air-gapped protected env and cannot export the logs. I'll try to give as much detail as I can as it pertains to the issue. For example I want to transfer an image from My skopeo sync command:
The above will produce the error where the image path is evaluated as |
Something like That might require splitting the yaml into several ones. Making this more general is tracked in various issues in this repo, e.g. #1998 can be a starting point. |
A friendly reminder that this issue had no activity for 30 days. |
When trying to sync to another gitlab registry there was an issue encountered where the image path was not parsed correctly by skopeo. A longer image path will cause an error when attempting to sync.
The above will cause an error and skopeo will evaluate the above with
customgitlab.example.com/projectpath:latest
instead of the provided path for the image(customgitlab.example.com/gitlabgroup/repo/projectpath:latest)
.The text was updated successfully, but these errors were encountered: