config: enable setting tlsVerify during image pull #262
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default podman (and docker) assume an image registry is configured to serve via HTTPS. By setting the tlsVerify=false query parameter we can make use of registries serving via HTTP, which is helpful e.g. in e2e tests.
lgfa29
approved these changes
Jul 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default podman (and docker) assume an image registry is configured
to serve via HTTPS. By setting the
tlsVerify=falsequery parameter wecan make use of registries serving via HTTP, which is helpful e.g. in
e2e tests. The default is to remain
true.Test coverage in hashicorp/nomad#17642