-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Login to insecure corporate registry with http only fails #24102
Comments
dschulten
changed the title
Login to Insecure Corporate Registry with http only Fails
Login to insecure corporate registry with http only fails
Sep 29, 2024
@mtrmac PTAL |
AFAIK login happen on the client but your config is only on the server. So the login command has no idea the the registry is configured as insecure. |
Very interesting! Where do I configure an insecure registry on the client? From your answer I learn that I am configuring the server when I execute podman machine ssh - where is client configuration located? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
I need to login to a corporate registry that functions as mirror for internet registries and only runs with http.
I have marked the registry as insecure by adding the following entry to /etc/containers/registries.conf:
Login fails:
So it appears that marking a registry as insecure does not have the effect that the login communication switches to http only.
Pulling and running images also fails:
The output above comes from the Windows Terminal Cmder, I have also tried pure cmd, same result.
Steps to reproduce the issue
Try podman login with insecure http registry
Describe the results you received
Login fails, it appears that podman tries to login with https in spite of the flag insecure registry
Describe the results you expected
Login success
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
None
Additional information
None
The text was updated successfully, but these errors were encountered: