NO-JIRA: extensions/Dockerfile: add extensions.json to last layer

[cverna]

Backport of commit 31816ac from master. On release branches the extensions container is still built by coreos-assembler, which bind-mounts /tmp/extensions.json into the build to propagate the extensions metadata into the build's meta.json, so keep writing to that path.

In addition, bake extensions.json into the final container image, so that it is easy for anyone but particularly ART to query metadata about the extensions container, e.g. via oc image extract or podman run $img cat /usr/share/rpm-ostree/extensions.json.

Assisted-by: AI

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[cverna]

This would be useful to help with verifying CVEs in the extensions container, testing on 4.18 before backporting further

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cverna

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [cverna]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@cverna: This pull request explicitly references no jira issue.

Details

In response to this:

Backport of commit 31816ac from master. On release branches the extensions container is still built by coreos-assembler, which bind-mounts /tmp/extensions.json into the build to propagate the extensions metadata into the build's meta.json, so keep writing to that path.

In addition, bake extensions.json into the final container image, so that it is easy for anyone but particularly ART to query metadata about the extensions container, e.g. via oc image extract or podman run $img cat /usr/share/rpm-ostree/extensions.json.

Assisted-by: AI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@cverna: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/rhcos-9-build-test-qemu	5686e3e	link	true	/test rhcos-9-build-test-qemu

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.