From ebaedc73edf77c20b6919227cf468f259049724b Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Tue, 29 Apr 2025 15:25:22 -0400 Subject: [PATCH] Containerfile: explain why REPOS_IMAGE is needed Having this is a bit confusing because the use case for it is exactly what `podman build --from` was intended for. Let's add a comment here about why it was added in aa9c6c2 [1], which is because konflux doesn't support --from yet [1]. [1] https://gitlab.com/fedora/bootc/base-images/-/merge_requests/106#note_2380147640 --- Containerfile | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Containerfile b/Containerfile index 4453cf9..0f173b6 100644 --- a/Containerfile +++ b/Containerfile @@ -9,6 +9,9 @@ # Override this repos container to control the base image package versions. For # example, podman build --from=quay.io/fedora/fedora:41 will get you a system # that uses Fedora 41 packages. Or inject arbitrary yum repos (COPR, etc) here. +# +# Note we also support --build-arg REPOS_IMAGE=quay.io/fedora/fedora:41 here +# since konflux doesn't yet support --from. ARG REPOS_IMAGE=quay.io/fedora/fedora:rawhide FROM $REPOS_IMAGE as repos