+++ This bug was initially created as a clone of Bug #1891759 +++
Description of problem:
Dockerfile builds cannot change permissions of /etc/pki/ca-trust or create files inside it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a Dockerfile with RUN chmod a+w -R /etc/pki/ca-trust/extracted
2. build an image
3. inspect /etc/pki/ca-trust/extracted permissions
It affects our ability to build release images:
--- Additional comment from email@example.com on 2020-10-27 12:51:43 UTC ---
This was a consequence of fixing https://bugzilla.redhat.com/show_bug.cgi?id=1826183. /etc/pki/ca-trust is a mount point for buildah, the contents of which are managed by the build container. When the build container starts, it adds the cluster-wide CA to the set of anchors, and then runs `update-ca-trust extract` as root.
In the case of the image registry, it wants /etc/pki/ca-trust to be writeable so that `update-ca-trust` can be run as non-root.
--- Additional comment from firstname.lastname@example.org on 2020-11-04 04:45:12 UTC ---
I think https://bugzilla.redhat.com/show_bug.cgi?id=1826183 needs to be considered for reversion, given the impact on existing build behavior.
It means that no one w/ a builder image that includes their own CAs can continue to function as expected, right? Because their CAs will be stomped by the always present mount that that fix introduced.
--- Additional comment from email@example.com on 2020-11-04 14:36:16 UTC ---
more specifically, here is my suggested course of action:
1) put in a change to 4.7 and 4.6 that does not mount the content (you can leave the rest of the logic in place)
2) get CI to update to the 4.6.z patch asap
3) reintroduce the mount based on a buildconfig api opt-in field. in 4.6+4.7.
Verified in version:
STEP 1: FROM registry.svc.ci.openshift.org/ocp/4.7:base
STEP 2: RUN chmod a+w -R /etc/pki/ca-trust/extracted
STEP 3: RUN ls -ld /etc/pki/ca-trust/extracted
drwxrwxrwx. 1 root root 70 Sep 1 19:39 /etc/pki/ca-trust/extracted
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.6.4 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
Replaced the doc text with the one from the "older sibling" clone.
Published in the enterprise-4.7 OpenShift release notes.