chore: allow go toolchain to upgrade just for installing tools (googl…

…eapis#10971) We do this in our CI images as well. Some of our tools now require 1.22+ and this gets around the issue while preserving the version used to run the app. Not having this was causing postprocess image builds to fail.
codyoss · Oct 9, 2024 · b520042 · b520042
1 parent e11abee
commit b520042
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/internal/postprocessor/Dockerfile b/internal/postprocessor/Dockerfile
@@ -22,7 +22,7 @@ WORKDIR /postprocessor
 RUN CGO_ENABLED=0 GOOS=linux go build -v -o post_processor
 
 # Install tools used in build
-RUN go install honnef.co/go/tools/cmd/staticcheck@latest && \
+RUN GOTOOLCHAIN='auto' go install honnef.co/go/tools/cmd/staticcheck@latest && \
     go install github.com/jstemmer/go-junit-report@latest && \
     go install golang.org/x/lint/golint@latest && \
     go install golang.org/x/tools/cmd/goimports@latest