Skip to content

Commit

Permalink
Remove go mod verify from Dockerfile
Browse files Browse the repository at this point in the history
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 <[email protected]>
  • Loading branch information
jkyros committed Aug 29, 2024
1 parent f21e5ea commit 9c19df2
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion Dockerfile.rhel7
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 9c19df2

Please sign in to comment.