From 1a458e3146dcd59261a7bf169ca48239ad5a0c77 Mon Sep 17 00:00:00 2001 From: Luca Miccini Date: Wed, 27 May 2026 06:03:56 +0200 Subject: [PATCH] Fix opm render failure due to v1-format registries.conf Recent versions of the containers/image library (used by opm) now hard-error on v1-format registries.conf instead of silently converting it. GitHub Actions ubuntu-latest runners ship with a v1-format config at /etc/containers/registries.conf, breaking the "Create index image" step for all operators using this reusable workflow. Set CONTAINERS_REGISTRIES_CONF=/dev/null for the opm steps. This is safe because opm render pulls by fully-qualified image reference and does not need local registry aliasing. See also: operator-framework/operator-lifecycle-manager#3839 Co-Authored-By: Claude Opus 4.6 --- .github/workflows/reusable-build-operator.yaml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/reusable-build-operator.yaml b/.github/workflows/reusable-build-operator.yaml index a99b955..16cd8fe 100644 --- a/.github/workflows/reusable-build-operator.yaml +++ b/.github/workflows/reusable-build-operator.yaml @@ -298,6 +298,10 @@ jobs: INDEX_IMAGE_TAG: ${{ env.latesttag }} INDEX_IMAGE: ${{ inputs.operator_name }}-operator-index CSV_VERSION: v${{ steps.get_csv_version.outputs.version }} + # opm uses containers/image which now rejects v1-format registries.conf + # shipped on ubuntu-latest runners. Safe to bypass since opm render + # pulls by fully-qualified reference and needs no registry aliases. + CONTAINERS_REGISTRIES_CONF: /dev/null - name: Push ${{ inputs.operator_name }}-operator-index To ${{ env.imageregistry }} uses: redhat-actions/push-to-registry@v2