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.

Sign up for GitHub

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

Jump to bottom

Add support to insecure registry #85

Closed
guilhermebr opened this issue May 14, 2018 · 3 comments · May be fixed by #358
Closed

Add support to insecure registry #85

guilhermebr opened this issue May 14, 2018 · 3 comments · May be fixed by #358

Comments

@guilhermebr
Copy link
Contributor

guilhermebr commented May 14, 2018 •
edited
Loading

Missing an option to push to an insecure registry.

It's common for development and integration tests

Log:

time="2018-05-14T18:59:03Z" level=info msg="pushing layers" exporting the image 10.200.10.1:5000/tsuru/go:latest failed: failed to do request: Head https://10.200.10.1:5000/v2/tsuru/go/blobs/sha256:a440082623eba20362e20fea387de304e5fe1d6cce355e7189e39ed7d79fdc07: http: server gave HTTP response to HTTPS client
@unkaktus
Copy link
Contributor

Personally I think it's better to spin up TLS at the registry and add an option like --insecure-skip-verify or something to img.

@guilhermebr guilhermebr mentioned this issue May 24, 2018
Merged
@ChaosEternal
Copy link

And also need to add a method to trust customized ca-certs, to support private, ssl-enabled registry.
both pull and push need that.

@unkaktus
Copy link
Contributor

@ChaosEternal, not really if you do trust any cert (with --tls-insecure-skip-verify).

btw, it seems that this issue should be closed already?

@jessfraz jessfraz mentioned this issue May 27, 2018
Closed
@zemanlx zemanlx mentioned this issue Jul 13, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow plain HTTP for insecure-registry option zemanlx/img
4 participants
@guilhermebr @jessfraz @ChaosEternal @unkaktus