From b5200423c9ed43be036faecc750d2e6c5fd9c594 Mon Sep 17 00:00:00 2001
From: Cody Oss <6331106+codyoss@users.noreply.github.com>
Date: Wed, 9 Oct 2024 10:04:23 -0500
Subject: [PATCH] chore: allow go toolchain to upgrade just for installing
 tools (#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.
---
 internal/postprocessor/Dockerfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/internal/postprocessor/Dockerfile b/internal/postprocessor/Dockerfile
index c3c6d575274a..e4aaa82587a3 100644
--- 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