Otdfbt

csname in newenviroment

Team member is vehemently against code formatting

Does science define life as "beginning at conception"?

How do I write real-world stories separate from my country of origin?

Shell builtin `printf` line limit?

Why did Nick Fury not hesitate in blowing up the plane he thought was carrying a nuke?

Why is this integration method not valid?

How many wires should be in a new thermostat cable?

Anatomically correct Guivre

How to safely discharge oneself

Is it normal to "extract a paper" from a master thesis?

How do you earn the reader's trust?

How to tease a romance without a cat and mouse chase?

Illustrating that universal optimality is stronger than sphere packing

Nunc est bibendum: gerund or gerundive?

Does the fact that we can only measure the two-way speed of light undermine the axiom of invariance?

Why do testers need root cause analysis?

How to become an Editorial board member?

Meaning of "half-crown enclosure"

Is ideal gas incompressible?

One word for 'the thing that attracts me'?

Can the Conjure Barrage spell stack with the Disarming Attack or Trip Attack Battle Master maneuvers?

Are there any tips to help hummingbirds find a new feeder?

Proto-Indo-European (PIE) words with IPA

Issue with Docker multi-stage builds

Building Docker images for multi environment supportKafka docker container on mesos cluster with marathonCommands in Dockerfile of a base image is not being runDocker multi-app setupDovecot: Kill permission denied when reloadingStarting sshd in a Centos 7 OS Docker Container on docker run using both ENTRYPOINT and CMDNuance Transcription Engine not running on DockerUnable to ssh into running dropbear sshd. “Bad password attempt” …But password is correctuse makefile to copy files in docker multi-stage buildsDocker container routing issue with multi nic host

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I have an issue with a multi-stage build where the binary that is being built in stage one is properly copied to stage 2, but when you try and run it the executable cannot be found.

The dockerfile is:

FROM golang as goimage
ENV SRC=/go/src/
RUN mkdir -p /go/src/
WORKDIR /go/src/go_docker
RUN git clone https://github.com/bryonbaker/simple-microservice.git /go/src/go_docker/ 
&& CGO_ENABLED=0 GOOS=linux GOARCH=amd64
RUN go get github.com/gorilla/mux
RUN go build -o bin/go_docker

FROM alpine:latest AS microservice
RUN apk --no-cache add bash
ENV WORK_DIR=/docker/bin
WORKDIR $WORK_DIR
COPY --from=goimage /go/src/go_docker/bin/ ./

# Put a container-image version identifier in the root directory.
ARG VERSION=1.0
RUN echo $VERSION > image_version

EXPOSE 10000
#CMD ["go_docker"]

The result is:

$ docker run -ti -p 80:10000 go-docker:latest
/docker/bin # ls
go_docker image_version
/docker/bin # ./go_docker 
/bin/sh: ./go_docker: not found
/docker/bin # 

If I run the binary from the intermediate goimage container that is built then it runs fine. The file sizes match...

NOTE: In this dockerfile I have commented out CMD and am testing via a shell. If you uncomment the CMD you get the same problem:

docker run go-docker:latest
docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: "go_docker": executable file not found in $PATH": unknown.
ERRO[0001] error waiting for container: context canceled

I have made the test code in the git repo public if you want to look at it.

Thanks in advance

docker

share|improve this question

asked May 8 at 12:54

BryonBryon

1211

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oops. This should have been posted on Stack Overflow. stackoverflow.com/questions/56057688/…
  
  – Bryon
  May 9 at 10:47
  

  
  
  
  

add a comment | 

0

I have an issue with a multi-stage build where the binary that is being built in stage one is properly copied to stage 2, but when you try and run it the executable cannot be found.

The dockerfile is:

FROM golang as goimage
ENV SRC=/go/src/
RUN mkdir -p /go/src/
WORKDIR /go/src/go_docker
RUN git clone https://github.com/bryonbaker/simple-microservice.git /go/src/go_docker/ 
&& CGO_ENABLED=0 GOOS=linux GOARCH=amd64
RUN go get github.com/gorilla/mux
RUN go build -o bin/go_docker

FROM alpine:latest AS microservice
RUN apk --no-cache add bash
ENV WORK_DIR=/docker/bin
WORKDIR $WORK_DIR
COPY --from=goimage /go/src/go_docker/bin/ ./

# Put a container-image version identifier in the root directory.
ARG VERSION=1.0
RUN echo $VERSION > image_version

EXPOSE 10000
#CMD ["go_docker"]

The result is:

$ docker run -ti -p 80:10000 go-docker:latest
/docker/bin # ls
go_docker image_version
/docker/bin # ./go_docker 
/bin/sh: ./go_docker: not found
/docker/bin # 

If I run the binary from the intermediate goimage container that is built then it runs fine. The file sizes match...

NOTE: In this dockerfile I have commented out CMD and am testing via a shell. If you uncomment the CMD you get the same problem:

docker run go-docker:latest
docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: "go_docker": executable file not found in $PATH": unknown.
ERRO[0001] error waiting for container: context canceled

I have made the test code in the git repo public if you want to look at it.

Thanks in advance

docker

share|improve this question

asked May 8 at 12:54

BryonBryon

1211

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oops. This should have been posted on Stack Overflow. stackoverflow.com/questions/56057688/…
  
  – Bryon
  May 9 at 10:47
  

  
  
  
  

add a comment | 

I have an issue with a multi-stage build where the binary that is being built in stage one is properly copied to stage 2, but when you try and run it the executable cannot be found.

The dockerfile is:

FROM golang as goimage
ENV SRC=/go/src/
RUN mkdir -p /go/src/
WORKDIR /go/src/go_docker
RUN git clone https://github.com/bryonbaker/simple-microservice.git /go/src/go_docker/ 
&& CGO_ENABLED=0 GOOS=linux GOARCH=amd64
RUN go get github.com/gorilla/mux
RUN go build -o bin/go_docker

FROM alpine:latest AS microservice
RUN apk --no-cache add bash
ENV WORK_DIR=/docker/bin
WORKDIR $WORK_DIR
COPY --from=goimage /go/src/go_docker/bin/ ./

# Put a container-image version identifier in the root directory.
ARG VERSION=1.0
RUN echo $VERSION > image_version

EXPOSE 10000
#CMD ["go_docker"]

The result is:

$ docker run -ti -p 80:10000 go-docker:latest
/docker/bin # ls
go_docker image_version
/docker/bin # ./go_docker 
/bin/sh: ./go_docker: not found
/docker/bin # 

If I run the binary from the intermediate goimage container that is built then it runs fine. The file sizes match...

NOTE: In this dockerfile I have commented out CMD and am testing via a shell. If you uncomment the CMD you get the same problem:

docker run go-docker:latest
docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: "go_docker": executable file not found in $PATH": unknown.
ERRO[0001] error waiting for container: context canceled

I have made the test code in the git repo public if you want to look at it.

Thanks in advance

docker

share|improve this question

asked May 8 at 12:54

BryonBryon

1211

FROM golang as goimage
ENV SRC=/go/src/
RUN mkdir -p /go/src/
WORKDIR /go/src/go_docker
RUN git clone https://github.com/bryonbaker/simple-microservice.git /go/src/go_docker/ 
&& CGO_ENABLED=0 GOOS=linux GOARCH=amd64
RUN go get github.com/gorilla/mux
RUN go build -o bin/go_docker

FROM alpine:latest AS microservice
RUN apk --no-cache add bash
ENV WORK_DIR=/docker/bin
WORKDIR $WORK_DIR
COPY --from=goimage /go/src/go_docker/bin/ ./

# Put a container-image version identifier in the root directory.
ARG VERSION=1.0
RUN echo $VERSION > image_version

EXPOSE 10000
#CMD ["go_docker"]

$ docker run -ti -p 80:10000 go-docker:latest
/docker/bin # ls
go_docker image_version
/docker/bin # ./go_docker 
/bin/sh: ./go_docker: not found
/docker/bin # 

docker run go-docker:latest
docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: "go_docker": executable file not found in $PATH": unknown.
ERRO[0001] error waiting for container: context canceled

share|improve this question

asked May 8 at 12:54

BryonBryon

1211

share|improve this question

asked May 8 at 12:54

BryonBryon

1211

asked May 8 at 12:54

BryonBryon

1211

asked May 8 at 12:54

BryonBryon

1211