If I have the eos chain running in a Docker container, how can I interact with it from my local file system? I would love to be able to create my contracts, compile them, and deploy to my docker container without being in the Docker exec terminal. Is there a way to have this traditional development environment using Docker? It is so much easier for me to upgrade chains using it, rather than compiling locally. Thanks!
4
-
Can't you use an alias? alias cleos='docker-compose exec keosd /opt/eos/bin/cleos -H nodeos'– tmm ♦Commented May 8, 2018 at 16:37
-
Hm, this seems more of a Docker question than EOS. You have to figure out 1.) how to share data from the host with the docker container and 2.) how to connect to the docker container to run commands (ssh i guess). Maybe this helps: digitalocean.com/community/tutorials/…– SoleoneCommented May 8, 2018 at 16:38
-
yeah, I can add an alias, but that doesn't allow me to refer to a local contract file. This is something that I want as a smart contract developer– cipherzCommented May 8, 2018 at 16:40
-
Can't you bind a docker volume to a local path of your filesystem and push it from there?– tmm ♦Commented May 8, 2018 at 16:44
Add a comment
|
1 Answer
The EOS.io Wiki page on using the Docker image suggests using the following command: alias cleos='docker-compose exec keosd /opt/eosio/bin/cleos -H nodeosd' to setup a local alias of the cleos command that operates on the docker image.
With this alias setup, you can execute the EOS client commands just like you would on a local instance.
