我有一个 npm 二进制文件，我想打包到 Docker 容器中。我有这样的配置:

# Docker image for the Mongo Stitch command

FROM golang:alpine

# Do a system update
RUN apk update

RUN apk add git

# Declare base dir
WORKDIR /root

# The console binary for Mongo Stitch
RUN git clone https://github.com/10gen/stitch-cli.git

WORKDIR /root/stitch-cli

RUN go build

CMD ["/bin/sh"]

我收到这个错误:

main.go:8:2: cannot find package "github.com/10gen/stitch-cli/commands" in any of:
    /usr/local/go/src/github.com/10gen/stitch-cli/commands (from $GOROOT)
    /go/src/github.com/10gen/stitch-cli/commands (from $GOPATH)
main.go:9:2: cannot find package "github.com/10gen/stitch-cli/utils" in any of:
    /usr/local/go/src/github.com/10gen/stitch-cli/utils (from $GOROOT)
    /go/src/github.com/10gen/stitch-cli/utils (from $GOPATH)
main.go:11:2: cannot find package "github.com/mitchellh/cli" in any of:
    /usr/local/go/src/github.com/mitchellh/cli (from $GOROOT)
    /go/src/github.com/mitchellh/cli (from $GOPATH)

这是出乎意料的，因为我想官方 Go 容器应该有我需要的一切。我设置了这些变量:

~ # set | grep GO
GOLANG_VERSION='1.11.5'
GOPATH='/go'

build instructions说 go build 足以让它工作。我玩过 go get，有各种错误输出，但我认为这可能是徒劳的追逐，因为如果我必须手动获取依赖项，说明会这样说。

尽管如此，如果我确实在容器 shell 中发出 go get，我会得到:

~/stitch-cli # go get
go get: no install location for directory /root/stitch-cli outside GOPATH
    For more details see: 'go help gopath'

我已经尝试解析上述帮助文件中的 Material ，但我不确定哪一部分适用于我的案例。

所以，我想知道 missing GOROOT was worth fixing .我这样做了:

~/stitch-cli # which go
/usr/local/go/bin/go
~/stitch-cli # GOROOT=/usr/local/go
~/stitch-cli # export GOROOT
~/stitch-cli # go build
# _/root/stitch-cli
./main.go:25:3: cannot use commands.NewWhoamiCommandFactory(ui) (type "github.com/10gen/stitch-cli/vendor/github.com/mitchellh/cli".CommandFactory) as type "github.com/mitchellh/cli".CommandFactory in map value
./main.go:26:3: cannot use commands.NewLoginCommandFactory(ui) (type "github.com/10gen/stitch-cli/vendor/github.com/mitchellh/cli".CommandFactory) as type "github.com/mitchellh/cli".CommandFactory in map value
./main.go:27:3: cannot use commands.NewLogoutCommandFactory(ui) (type "github.com/10gen/stitch-cli/vendor/github.com/mitchellh/cli".CommandFactory) as type "github.com/mitchellh/cli".CommandFactory in map value
./main.go:28:3: cannot use commands.NewExportCommandFactory(ui) (type "github.com/10gen/stitch-cli/vendor/github.com/mitchellh/cli".CommandFactory) as type "github.com/mitchellh/cli".CommandFactory in map value
./main.go:29:3: cannot use commands.NewImportCommandFactory(ui) (type "github.com/10gen/stitch-cli/vendor/github.com/mitchellh/cli".CommandFactory) as type "github.com/mitchellh/cli".CommandFactory in map value
~/stitch-cli # 

好吧，也许这有点远，但我现在坚定地处于“尝试随机事物”领域。有什么我可以做的让它开箱即用吗？

我也尝试过手动安装 Go 的普通 Alpine (v3.9)，它甚至没有设置 GOPATH，但我遇到了同样的“找不到包”错误。接下来我可以尝试什么来编译它？

我也尝试过切换到 Golang 图像的全脂版本，而不是这个更轻的 Alpine 图像，我遇到了同样的问题，build 和 get.

我也可以回到通过 NPM 安装，但我遇到了问题(这个问题可能超出了 Golang 问题的范围)。

可能重复

我的问题已被确定为可能重复 of this question .我认为这个问题本质上是这里提到的次要问题的重复，正如我之前提到的，这可能是一个转移注意力的问题。如果有任何重复项详细说明第一个错误的答案，那可能是一个更好的路标。

最佳答案

Flimzy 友善地向我指出了另一个答案(如果没有知识渊博的帮助，我永远不会找到这个答案)。由于我认为构建过程非常重要，尤其是对于像我这样的非 Gophers，我将发布新的 Dockerfile:

# Docker image for the Mongo Stitch command

FROM golang:alpine

# Do a system update
RUN apk update

RUN apk add git curl

# Declare base dir
WORKDIR /root/src

RUN git clone https://github.com/10gen/stitch-cli.git

WORKDIR /root/src/stitch-cli

# Remove the old dependencies
RUN rm -rf vendor

# Fetch the dependencies
RUN curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh
RUN GOPATH=$GOPATH:/root dep ensure

# Now it should build
RUN GOPATH=$GOPATH:/root go build

CMD ["/bin/sh"]

获取依赖项导致此错误:

Warning: the following project(s) have [[constraint]] stanzas in Gopkg.toml:

  ✗  github.com/10gen/escaper
  ✗  github.com/dgrijalva/jwt-go
  ✗  github.com/ogier/pflag
  ✗  gopkg.in/mgo.v2

However, these projects are not direct dependencies of the current project:
they are not imported in any .go files, nor are they in the 'required' list in
Gopkg.toml. Dep only applies [[constraint]] rules to direct dependencies, so
these rules will have no effect.

Either import/require packages from these projects so that they become direct
dependencies, or convert each [[constraint]] to an [[override]] to enforce rules
on these projects, if they happen to be transitive dependencies.

但是，它似乎仍然可以编译。我担心的是，我必须执行的步骤比文档中的要多得多，这让我认为我已经把它变得比需要的更复杂了。

docker repo

我已将我的 Docker 存储库永久化 available here .

关于docker - 为什么 "go build"对我的 Docker 项目失败？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/54504906/