-
Bug
-
Resolution: Done
-
Normal
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
1
-
None
-
None
-
None
-
None
-
uShift Sprint 276
-
1
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-61198. The following is the description of the original issue:
—
Description of problem:
embedding container images into my bootc build failes with a strange proxy error message
Version-Release number of selected component (if applicable):
4.19
How reproducible:
always
Steps to Reproduce:
I am trying to embedding container images into my bootc build following the procedure from
https://github.com/openshift/microshift/blob/main/docs/user/image_mode.md#appendix-a-embedding-container-images-in-bootc-builds
As Base Image, I use openshift4/microshift-bootc-rhel9:v4.19
Actual results:
Pulling MicroShift image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:d4b41ea0180046a3c6523df9390dc600230db03fdaa2ea415ace9b50765af9d0... time="2025-09-03T08:08:06Z" level=fatal msg="initializing source docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:d4b41ea0180046a3c6523df9390dc600230db03fdaa2ea415ace9b50765af9d0: pinging container registry quay.io: Get \"https://quay.io/v2/\": proxyconnect tcp: dial tcp 127.0.0.1:9999: connect: connection refused"
Expected results:
skopeo copy pull command should be successfull
Additional info:
It seems that the microshift bootc base image has been built with: STEP 3/14: RUN env | grep -i proxy NO_PROXY=localhost,127.0.0.1,::1,.redhat.com HTTPS_PROXY=http://127.0.0.1:9999 HTTP_PROXY=http://127.0.0.1:9999
Simple workaround:
Add
``` unset HTTP_PROXY HTTPS_PROXY NO_PROXY ; \
to the container file.
- clones
-
-
- Verified
-
- depends on
-
-
- Verified
-
- is cloned by
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
- links to