-
Notifications
You must be signed in to change notification settings - Fork 324
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
Docker build fails #5
Comments
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)
|
@jerkyrs thanks for reporting the issue. Before building the docker image. try to do the following in your dev environment:
|
@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.
|
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. |
tested commit e380921 , the CMD syntax for starting iotex-server is incorrect
Available options
Does not start automatically as a result |
Good catch! Will fix this |
This is fixed in the latest master |
…th ws contracts (#4283) * feat(ioctl/ws): ioctl support ws project device contract interactions --------- Co-authored-by: CoderZhi <[email protected]>
…th ws contracts (#4283) * feat(ioctl/ws): ioctl support ws project device contract interactions --------- Co-authored-by: CoderZhi <[email protected]>
What I did
What i saw
What I expected to see
A clean build of the iotex-core
The text was updated successfully, but these errors were encountered: