去在docker中构建:/ go / bin中意外的二进制文件

According to this post: What does go build build?

go build builds the binary and leaves it in the current directory, while go install moves the binary into $GOPATH/bin.

This works on my machine like that. However, I have a Dockerfile:

FROM golang:latest
ADD . /go/src/myapp
WORKDIR /go/src/myapp
RUN go get .
RUN go build 
RUN ls /go/bin # shows myapp!!
ENTRYPOINT ["/go/bin/myapp"] #works!!

There should be no difference here. The expected result was that /go/bin was empty and the binary myapp would be /go/src/myapp/myapp Instead, I see that build is working like install, and the binary shows up in /go/bin. Why??

The go get command is installing your package into /go/bin. If you dont want to install your current package then pass -d to stop after downloading your dependencies.

The -d flag instructs get to stop after downloading the packages; that is, it instructs get not to install the packages.

https://golang.org/cmd/go/#hdr-Download_and_install_packages_and_dependencies