Skip to content

Commit 717381f

Browse files
committed
build: Reorder --cache-from sources
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)
1 parent 7190f72 commit 717381f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

devel/build

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -73,14 +73,14 @@ docker buildx build \
7373
--builder "$builder" \
7474
--platform "$platform" \
7575
--build-arg GIT_REVISION \
76-
--cache-from "$BUILDER_IMAGE:latest" \
77-
--cache-from "$BUILDER_IMAGE:$tag" \
78-
--cache-from "$FINAL_IMAGE:latest" \
79-
--cache-from "$FINAL_IMAGE:$tag" \
80-
--cache-from "$registry/$BUILDER_IMAGE:latest" \
8176
--cache-from "$registry/$BUILDER_IMAGE:$tag" \
82-
--cache-from "$registry/$FINAL_IMAGE:latest" \
77+
--cache-from "$registry/$BUILDER_IMAGE:latest" \
8378
--cache-from "$registry/$FINAL_IMAGE:$tag" \
79+
--cache-from "$registry/$FINAL_IMAGE:latest" \
80+
--cache-from "$BUILDER_IMAGE:$tag" \
81+
--cache-from "$BUILDER_IMAGE:latest" \
82+
--cache-from "$FINAL_IMAGE:$tag" \
83+
--cache-from "$FINAL_IMAGE:latest" \
8484
--cache-to type=inline \
8585
--tag "$registry/$FINAL_IMAGE:$tag" \
8686
--push \

0 commit comments

Comments
 (0)