Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Dockerfile isn't working (go dep issue ?) #81

Open
sebPomme opened this issue Oct 25, 2020 · 2 comments · May be fixed by #119
Open

The Dockerfile isn't working (go dep issue ?) #81

sebPomme opened this issue Oct 25, 2020 · 2 comments · May be fixed by #119

Comments

@sebPomme
Copy link

sebPomme commented Oct 25, 2020

Hi,

I try to build the docker image (because no pre-build image is avalaible for arm arch) ant it isn't working, here is the traceback:

sebpomme machine:~ [645:1]% docker build -t sache "https://github.com/messagebird/sachet.git#0.2.3"
Sending build context to Docker daemon   3.77MB
Step 1/12 : FROM golang:1.14 AS builder
1.14: Pulling from library/golang
e4c3d3e4f7b0: Already exists 
101c41d0463b: Pull complete 
8275efcd805f: Pull complete 
751620502a7a: Pull complete 
aaabf962c4fc: Pull complete 
8201797aea2f: Pull complete 
3a0b5e7e1f6f: Pull complete 
Digest: sha256:cdc098a969e749099ca24578990cf42195aa9cd2f5e04b0e196171bb0dbb885d
Status: Downloaded newer image for golang:1.14
 ---> d5ddd1861619
Step 2/12 : WORKDIR /build
 ---> Running in a92566e7ac8a
Removing intermediate container a92566e7ac8a
 ---> 7ebc2015b279
Step 3/12 : COPY . .
 ---> e655615669dc
Step 4/12 : RUN GO111MODULE=on CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -mod vendor -o sachet github.com/messagebird/sachet/cmd/sachet
 ---> Running in ffb91a57691f
go: inconsistent vendoring in /build:
	github.com/aliyun/alibaba-cloud-sdk-go@v1.61.122: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/aliyun/alibaba-cloud-sdk-go@v1.60.327
	github.com/carlosdp/twiliogo@v0.0.0-20161027183705-b26045ebb9d1: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/carlosdp/twiliogo@v0.0.0-20140102225436-f61c8230fa91
	github.com/golang/protobuf@v1.4.0: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/golang/protobuf@v1.1.0
	github.com/jmespath/go-jmespath@v0.3.0: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/jmespath/go-jmespath@v0.0.0-20180206201540-c2b33e8439af
	github.com/messagebird/go-rest-api@v5.3.0+incompatible: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/messagebird/go-rest-api@v0.0.0-20180517131710-a9514230491e
	github.com/prometheus/alertmanager@v0.20.0: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/prometheus/alertmanager@v0.14.0
	github.com/prometheus/client_golang@v1.5.1: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/prometheus/client_golang@v0.8.0
	github.com/prometheus/procfs@v0.0.11: is explicitly required in go.mod, but vendor/modules.txt indicates github.com/prometheus/procfs@v0.0.0-20180408092902-8b1c2da0d56d
	gopkg.in/ini.v1@v1.55.0: is explicitly required in go.mod, but vendor/modules.txt indicates gopkg.in/ini.v1@v1.42.0
	gopkg.in/telegram-bot-api.v4@v4.6.4: is explicitly required in go.mod, but vendor/modules.txt indicates gopkg.in/telegram-bot-api.v4@v4.6.2
	gopkg.in/yaml.v2@v2.2.8: is explicitly required in go.mod, but vendor/modules.txt indicates gopkg.in/yaml.v2@v2.2.1

run 'go mod vendor' to sync, or use -mod=mod or -mod=readonly to ignore the vendor directory
The command '/bin/sh -c GO111MODULE=on CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -mod vendor -o sachet github.com/messagebird/sachet/cmd/sachet' returned a non-zero code: 1

Can you help me to fix this ?

@farmanih
Copy link

I have this problem too. Any updates?

@Earvin32
Copy link

Got this problem too. Has someone find an idea ? Not many documentation to use Sachet with Prometheus...

@sebPomme sebPomme linked a pull request Jun 5, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants