Docker build fails about iotex-core HOT 7 CLOSED

It seems as though it thinks these dependencies are already in the working directory, they probably should be pulled in using go get via run commands (bolt, proto, grpc)

RUN go get google.golang.org/grpc

from iotex-core.

@jerkyrs thanks for reporting the issue. Before building the docker image. try to do the following in your dev environment:

1. Download and install glide
2. Rund glide install

from iotex-core.

@zjshen14 ok this works but i don't like it.. You should not have to install something into your working directory before you run a Dockerfile, Dockerfile assumes you are running on a stateless server without anything more then Docker itself available.

I dont know if this is feasible because i never tested it but why not use glide inside container, i realize this comes with overhead have having to fetch each time but you can not rely on what is currently installed in the users working directory to facilitate a clean build.

RUN curl https://glide.sh/get | sh

from iotex-core.

It's possible to use glide inside container, we didn't do it to shorten the process of building an docker image. This is under the assumption that glide install has been executed so that dependencies will be copied into docker too. However, you have raise a fair point.

from iotex-core.

tested commit e380921 , the CMD syntax for starting iotex-server is incorrect

CMD ["iotex-server", "-stderrthreshold=WARNING", "-log_dir=/var/log/iotex/server.log", "-config=/etc/iotex/config.yaml"]

Available options

usage: server -config=[string]
  -config string
        specify configuration file path (default "./config.yaml")
  -log-level string
        Log level (default "info")
  -log-path string
        Log path

Does not start automatically as a result

from iotex-core.

Good catch! Will fix this

from iotex-core.

This is fixed in the latest master

from iotex-core.