With most of my Go projects I usually specify an entrrypoint in my Dockerfile.
FROM golang:1.14.1-alpine as build WORKDIR $GOPATH/src/github.com/rugwirobaker/app COPY go.mod go.sum ./ RUN GO111MODULE=on GOPROXY="https://proxy.golang.org" go mod download COPY . . RUN GO111MODULE=on CGO_ENABLED=0 go build -o /bin/app ./cmd/app FROM scratch WORKDIR / EXPOSE 8080 COPY --from=build /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ COPY --from=build /bin/app /bin/app ENTRYPOINT ["/bin/app"]
Correct me if I am wrong but it seems waypoint injects it’s own ENTRYPOINT at build time which conflicts with the one set in the Dockerfile and hence this error:
$ docker logs web-01EMSNTHDCY5TNQA773WZR2V89 standard_init_linux.go:219: exec user process caused: no such file or directory
Perhaps an example for statically compiled languages like Go and Rust would help clear up things,