Skip to content

Document how to run podman.io on localhost with HTTPS. #425

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

Merged
merged 1 commit into from
Aug 12, 2025

Conversation

jankaluza
Copy link
Member

No description provided.

Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Although I guess using GIT_ALLOW_PROTOCOL to fetch from the local server via http might have also worked for testing according to the go docs.

Copy link
Member

@Honny1 Honny1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@ninja-quokka ninja-quokka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested locally and LGTM, thanks!

@Luap99 Luap99 merged commit aa04781 into containers:main Aug 12, 2025
3 checks passed
@jankaluza
Copy link
Member Author

jankaluza commented Aug 12, 2025

LGTM

Although I guess using GIT_ALLOW_PROTOCOL to fetch from the local server via http might have also worked for testing according to the go docs.

That's more about persuading go to use http instead of https for those vanity http requests. I think GIT_ALLOW_PROTOCOL would not help here. But finding a way how to tell go to use http instead of https would be another way to approach it for sure :-).

@Luap99
Copy link
Member

Luap99 commented Aug 12, 2025

Although I guess using GIT_ALLOW_PROTOCOL to fetch from the local server via http might have also worked for testing according to the go docs.

That's more about persuading go to use http instead of https for those vanity http requests. I think GIT_ALLOW_PROTOCOL would not help here. But finding a way how to tell go to use http instead of https would be another way to approach it for sure :-).

From the go docs:

By default, downloads are restricted to known secure protocols (e.g. https, ssh). To override this setting for Git downloads, the GIT_ALLOW_PROTOCOL environment variable can be set (For more details see: 'go help environment').

If the import path is not a known code hosting site and also lacks a version control qualifier, the go tool attempts to fetch the import over https/http and looks for a tag in the document's HTML .

That claims go looks up via http just the git clone need this var?! Anyway doesn't matter this can be documented regardless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants