Allow podman to push images to the local insecure registry #163
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.
The kubevirt CI infrastructure is moving to using a podman based bootstrap image rather than a docker in docker setup.
When running the
pull-kubevirt-cloud-provider-kubevirt-e2e
presubmit with podman, the job fails[1] as podman doe not allow pusgin to insecure registries by default[2].This update will add the local insecure registry to registries.conf when the podman socket is available which will allow podman to push images to the registry.
[1] https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_project-infra/2359/rehearsal-pull-kubevirt-cloud-provider-kubevirt-e2e/1575140184981245952#1:build-log.txt%3A766
[2] https://github.com/containers/podman/blob/main/troubleshooting.md#4-http-server-gave-http-response-to-https-client
/cc @qinqon @rhrazdil
Signed-off-by: Brian Carey bcarey@redhat.com