Remove go mod init
from dockerize build in base-server.Dockerfile
#2393
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dockerize moved from using Glock to Go modules and introduced go.mod and go.sum files into the repository.
Therefore, the Go module initialization command has to be removed from the
base-server
Dockerfile as it breaks the build.See: jwilder/dockerize@6f92b85
What changed?
The
go mod init
command was removed from the build of thedockerize
tool in thebase-server
image.Why?
A clean build of the
base-server
image fails.How did you test it?
I've run the build and checked the server locally.
Potential risks
The build of Docker images based on the
base-server
image will fail:temporal-server
andtemporal-tctl
.Is hotfix candidate?
No