Loading
feat(orchestration): pre-built base images pinned to juice version + kaniko CI Build
Migrates base-image handling from a runtime/CLI migration flow to pre-built, published CI base images that are automatically pinned to the running juice version. Also reworks the CI job.
- A juice version is only guaranteed compatible with the base image published under its matching tag. Assuming
latestis unsafe.
juice build --render-only (cli/build.py)
- New flag: render only the Containerfile + pyproject.toml into
--output-dir. Lets an external unprivileged builder (Kaniko/buildah) do the actual build.--tagnow optional (required unless--render-only);--output-dirrequired with--render-only.
CI (.gitlab-ci.yml)
-
Split
Build CI Base Imageinto two jobs:- Render CI Base Image Context —
juice build --render-only, exports build-context/ artifact. - Build CI Base Image — Build
Containerfilewithpyproject.tomlusingkaniko
- Render CI Base Image Context —
-
New
docs/source/concepts/base-images.md(tag derivation) anddocs/source/tutorials/admin/pre-built-base-images.md.
Edited by Kristian Gogora