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

Copy on insecure registries #192

Closed
andmagom opened this issue Jul 15, 2021 · 4 comments
Closed

Copy on insecure registries #192

andmagom opened this issue Jul 15, 2021 · 4 comments
Labels
bug This issue describes a defect or unexpected behavior can be replicated A bug can be repoduced carvel accepted This issue should be considered for future work and that the triage process has been completed

Comments

@andmagom
Copy link

What steps did you take:
I would like to copy images between insecure registries, I executed this command
imgpkg copy --registry-insecure -b registry.192.168.20.40.nip.io:5000/myimage --to-repo registry.192.168.20.40.nip.io:5000/myimage2

What happened:
I got this error
image

What did you expect:
If I set the --registry-insecure flag, I should like to be able to copy images between insecure registries

Environment:

  • imgpkg version (use imgpkg --version): imgpkg version 0.14.0
  • Docker registry used (e.g. Docker HUB): registry:v2 - docker image
  • OS (e.g. from /etc/os-release): Mac OS

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

@andmagom andmagom added bug This issue describes a defect or unexpected behavior carvel triage This issue has not yet been reviewed for validity labels Jul 15, 2021
@DennisDenuto DennisDenuto added can be replicated A bug can be repoduced carvel accepted This issue should be considered for future work and that the triage process has been completed and removed carvel triage This issue has not yet been reviewed for validity labels Jul 20, 2021
@DennisDenuto
Copy link
Contributor

Can reproduce. The image references provided to MultiWrite are losing the insecure option, hence when the ggcr library 'pings' the registry it doesn't 'fallback' to using http.

https://github.com/vmware-tanzu/carvel-imgpkg/blob/ee3d2f72ca3f9750939ca366097454074d2d0d04/pkg/imgpkg/registry/registry.go#L127

@DennisDenuto
Copy link
Contributor

Submitted PR #197

@andmagom
Copy link
Author

Thanks Dennis !

@DennisDenuto
Copy link
Contributor

@github-actions github-actions bot added the carvel triage This issue has not yet been reviewed for validity label Jul 28, 2021
@aaronshurley aaronshurley removed the carvel triage This issue has not yet been reviewed for validity label Nov 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue describes a defect or unexpected behavior can be replicated A bug can be repoduced carvel accepted This issue should be considered for future work and that the triage process has been completed
Projects
None yet
Development

No branches or pull requests

3 participants