dockerfiles: cache go mod dependencies in their own layer

this change causes docker to create an additional intermediate layer containing just the go.mod file and the downloaded dependencies cited therefrom. this prevents having to re-download the go.mod dependencies on EVERY image rebuild. more specifically, as long as you don't change the go.mod file, docker will use the cached layer.
flashbots · Sep 19, 2024 · 8fad770 · 8fad770
1 parent f019d90
commit 8fad770
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/cli.dockerfile b/cli.dockerfile
@@ -2,6 +2,9 @@
 FROM golang:1.21 AS builder
 ARG VERSION
 WORKDIR /build
+ADD go.mod /build/
+RUN --mount=type=cache,target=/root/.cache/go-build CGO_ENABLED=0 GOOS=linux \
+       go mod download
 ADD . /build/
 RUN --mount=type=cache,target=/root/.cache/go-build CGO_ENABLED=0 GOOS=linux \
     go build \

diff --git a/httpserver.dockerfile b/httpserver.dockerfile
@@ -2,6 +2,9 @@
 FROM golang:1.21 AS builder
 ARG VERSION
 WORKDIR /build
+ADD go.mod /build/
+RUN --mount=type=cache,target=/root/.cache/go-build CGO_ENABLED=0 GOOS=linux \
+       go mod download
 ADD . /build/
 RUN --mount=type=cache,target=/root/.cache/go-build CGO_ENABLED=0 GOOS=linux \
     go build \