From 9c19df297ec6fc371eb2a6335a23655a1f4b39de Mon Sep 17 00:00:00 2001 From: John Kyros Date: Thu, 29 Aug 2024 10:30:01 -0500 Subject: [PATCH] Remove go mod verify from Dockerfile So because we run our builds in a disconnected environment without internet access, the "go mod verify" statement will fail trying to check the module hashes. There might be a module cache or something as part of the build environment that we can we can wire up so we can still verify while in the disconnected environment, but until we figure it out, we want our builds to still succeed. This just removes the "go mod verify" command for now to make builds work again while we figure out of there's a way we can still make it work. Signed-off-by: John Kyros --- Dockerfile.rhel7 | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Dockerfile.rhel7 b/Dockerfile.rhel7 index f7c7f814..d91aeba3 100644 --- a/Dockerfile.rhel7 +++ b/Dockerfile.rhel7 @@ -11,7 +11,11 @@ COPY go.sum go.sum # since we use vendoring we don't need to redownload our dependencies every time. Instead we can simply # reuse our vendored directory and verify everything is good. If not we can abort here and ask for a revendor. COPY vendor vendor/ -RUN go mod verify + +# TODO(jkyros): go mod verify talks to the internet to check hashes, and it breaks in our disconnected +# build environment without access to the go proxy. Maybe there is a mod cache or something we can make +# it use in the build environment, but until then, turn it off. +# RUN go mod verify # Copy the go source COPY cmd/main.go cmd/main.go