Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-61481

[release-4.18] MicroShift bootc image has embedded proxy config

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • None
    • None
    • None
    • None
    • uShift Sprint 276
    • 1
    • In Progress
    • Bug Fix
    • Hide
      Before this update, embedding container images into a bootc build could fail because HTTP proxy environment variables were defined in the bootc image. Proxy errors occurred during container image embedding and prevented successful builds. With this release, the bootc image no longer sets HTTP proxy environment variables, thereby eliminating the issue. As a result, you can now embed container images without encountering proxy errors.
      Show
      Before this update, embedding container images into a bootc build could fail because HTTP proxy environment variables were defined in the bootc image. Proxy errors occurred during container image embedding and prevented successful builds. With this release, the bootc image no longer sets HTTP proxy environment variables, thereby eliminating the issue. As a result, you can now embed container images without encountering proxy errors.
    • 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. 

              ggiguash@redhat.com Gregory Giguashvili
              dfroehli42rh Daniel Fröhlich
              None
              None
              John George John George
              Shauna Diaz Shauna Diaz
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: