cmd.go: why we use go mod download before build go application? #40242
Labels
Comments
|
Thank you for raising this issue. Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only. For asking questions, see:
|
|
Presumably, it's about creating extra docker layers so that small changes don't make a big difference in the re-build time. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Go are you using (
go version)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env)?go envOutputWhat did you do?
When people make dockerfile of go application with module, most of them make like this.
FROM golang
COPY go.mod .
COPY go.sum .
RUN go mod download
COPY . .
RUN go build
But when i tested like below, it also works well.
FROM golang
COPY . .
RUN go build
what's the difference?
If i use go mod download command, can i get some advantages?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: