-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.14.0
-
None
-
No
-
False
-
This is a clone of issue OCPBUGS-14565. The following is the description of the original issue:
—
Description of problem:
Dockerfile.upi.ci.rhel8 does not work with the following error: [3/3] STEP 26/32: RUN chown 1000:1000 /output && chmod -R g=u "$HOME/.bluemix/" chmod: cannot access '/root/.bluemix/': No such file or directory error: build error: building at STEP "RUN chown 1000:1000 /output && chmod -R g=u "$HOME/.bluemix/"": while running runtime: exit status 1
Version-Release number of selected component (if applicable):
master (and possibly all other branches where the ibmcli tool was introduced)
How reproducible:
always
Steps to Reproduce:
1. Try to use Dockerfile.ci.upi.rhel8 2. 3.
Actual results:
[3/3] STEP 26/32: RUN chown 1000:1000 /output && chmod -R g=u "$HOME/.bluemix/" chmod: cannot access '/root/.bluemix/': No such file or directory error: build error: building at STEP "RUN chown 1000:1000 /output && chmod -R g=u "$HOME/.bluemix/"": while running runtime: exit status 1
Expected results:
No failures
Additional info:
We should also change the downloading of the govc image with curl to importing it from the cached container in quay.io, as it is done in Dockerfile.ci.upi
- blocks
-
OCPBUGS-23379 images: RHEL-8-based container image is broken
- Closed
- clones
-
OCPBUGS-14565 images: RHEL-8-based container image is broken
- Closed
- is blocked by
-
OCPBUGS-14565 images: RHEL-8-based container image is broken
- Closed
- is cloned by
-
OCPBUGS-23379 images: RHEL-8-based container image is broken
- Closed
- links to