Skip to content

Commit

Permalink
build: Reorder --cache-from sources
Browse files Browse the repository at this point in the history
It is unclear how docker handles multiple caches under the hood.
I did find an older comment¹ that if multiple `--cache-from` sources are
provided, it will use the first cache hit for the whole run.

This is my attempt to prioritize the ordering of the sources to use the
tagged images from the ghcr.io registry over the latest images from
docker.io.

¹ moby/moby#26839 (comment)
  • Loading branch information
joverlee521 committed May 16, 2023
1 parent 7190f72 commit 717381f
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions devel/build
Original file line number Diff line number Diff line change
Expand Up @@ -73,14 +73,14 @@ docker buildx build \
--builder "$builder" \
--platform "$platform" \
--build-arg GIT_REVISION \
--cache-from "$BUILDER_IMAGE:latest" \
--cache-from "$BUILDER_IMAGE:$tag" \
--cache-from "$FINAL_IMAGE:latest" \
--cache-from "$FINAL_IMAGE:$tag" \
--cache-from "$registry/$BUILDER_IMAGE:latest" \
--cache-from "$registry/$BUILDER_IMAGE:$tag" \
--cache-from "$registry/$FINAL_IMAGE:latest" \
--cache-from "$registry/$BUILDER_IMAGE:latest" \
--cache-from "$registry/$FINAL_IMAGE:$tag" \
--cache-from "$registry/$FINAL_IMAGE:latest" \
--cache-from "$BUILDER_IMAGE:$tag" \
--cache-from "$BUILDER_IMAGE:latest" \
--cache-from "$FINAL_IMAGE:$tag" \
--cache-from "$FINAL_IMAGE:latest" \
--cache-to type=inline \
--tag "$registry/$FINAL_IMAGE:$tag" \
--push \
Expand Down

0 comments on commit 717381f

Please sign in to comment.