Skip to content

fix(quick-start-local): rebuild my-profile's pyegeria layer with the others #610

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mandy-chessell merged 2 commits into from
Oct 6, 2026
Merged

fix(quick-start-local): rebuild my-profile's pyegeria layer with the others #610

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
36edce7
fix(quick-start-local): rebuild my-profile's pyegeria layer with the …
dwolfson Oct 5, 2026
a98b768
Merge branch 'main' into fix/quick-start-local-rebuild-my-profile-pye…
mandy-chessell Oct 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions quick-start-local
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Options:
--refresh-platform Force rebuild of egeria-main so the container engine pulls
the latest base image.
--pyegeria-version VERSION
Pin pyegeria-web and jupyter to a specific pyegeria
Pin pyegeria-web, jupyter and my-profile to a specific pyegeria
release (e.g. 6.1.20). Persists in
compose-configs/egeria-quickstart/.env.pyegeria, so plain re-runs
stay pinned; pass `latest` to clear the pin. Without a
Expand Down Expand Up @@ -648,13 +648,13 @@ EOF
docker.io/odpi/egeria-platform:latest
fi

# pyegeria-web's and jupyter's `pip install --upgrade pyegeria` each sit in
# pyegeria-web's, jupyter's and my-profile's `pip install --upgrade pyegeria` each sit in
# their own cached Docker RUN layer (see Dockerfile-fast-api / Dockerfile-
# jupyter's own PYEGERIA_BUST comments) -- a plain rebuild reuses that
# jupyter / Dockerfile-my-egeria's own PYEGERIA_BUST args) -- a plain rebuild reuses that
# layer and keeps whatever version was resolved when the image was last
# built, even though requirements.txt's `pyegeria>=X` floor has no upper
# bound. Passing a fresh PYEGERIA_BUST value busts just that one layer
# (both Dockerfiles echo it into the RUN instruction so its content
# (all three Dockerfiles echo it into the RUN instruction so its content
# actually changes), so the subsequent build below re-resolves pyegeria
# without a full --no-cache rebuild of everything else in the image.
# Default: install the latest pyegeria release (or the saved pin) on
Expand All @@ -664,10 +664,10 @@ EOF
resolve_pyegeria_build_args "$REPO_ROOT/compose-configs/egeria-quickstart/.env.pyegeria" \
"$PYEGERIA_VERSION_REQUEST" "$REFRESH_PYEGERIA" "[quick-start-local]"
if [[ ${#PYEGERIA_BUILD_ARGS[@]} -gt 0 ]]; then
echo "[quick-start-local] Building pyegeria layer (pyegeria-web + jupyter)..."
echo "[quick-start-local] Building pyegeria layer (pyegeria-web + jupyter + my-profile)..."
$COMPOSE_CMD -p egeria-quickstart "${COMPOSE_FILES[@]}" build \
"${PYEGERIA_BUILD_ARGS[@]}" \
pyegeria-web jupyter-hub
pyegeria-web jupyter-hub my-profile
fi

echo "[quick-start-local] Ensuring core images are available (platform, pyegeria-web, jupyter, my-profile)..."
Expand Down
Loading