scripts: rename container image to full path as used in CI
This is needed due to what seems like a Podman bug: I have previously
built this image for CI (using scripts/push_ci_image.sh), which tagged
it gcr.io/monogon-infra/monogon-builder:... . Then, when I ran
scripts/create_container.sh it would actually not tag the container
as monogon-builder, but instead as gcr.io/monogon-infra/monogon-builder.
This meant that scripts/bin/bazel kept using an older version of the
image than I expected.
I would debug this further, but at some point we should have done this
re-tag for local developer images anyway, as this will enable us to pull
this builder image from GCR in some cases if necessary (sparing some
developers the local image build step).
Change-Id: I24445f94e7808cb4c478395358a4aa520df5906b
Reviewed-on: https://review.monogon.dev/c/monogon/+/446
Reviewed-by: Leopold Schabel <leo@nexantic.com>
diff --git a/scripts/create_container.sh b/scripts/create_container.sh
index fcf0787..880217a 100755
--- a/scripts/create_container.sh
+++ b/scripts/create_container.sh
@@ -25,7 +25,7 @@
# Rebuild base image purely with no build context (-) ensuring that the
# builder image does not contain any other data from the repository.
- podman build -t monogon-builder - < "${dockerfile}"
+ podman build -t gcr.io/monogon-infra/monogon-builder - < "${dockerfile}"
# TODO(serge): stop using pods for the builder, this is a historical artifact.
podman pod create --name monogon
@@ -114,7 +114,7 @@
--name=monogon-dev \
--net=host \
"${podman_flags[@]}" \
- monogon-builder
+ gcr.io/monogon-infra/monogon-builder
}
main