5

Some of my attempts researching how to get EOS up and running:

Is there a binary I could simply run?

  • brew install eos
  • apt-get install eos

You get the idea... Easier to get stared = wider adoption.


I'm terrible at solving build issues, that's why I'm working on the front-end, that's why it is easier for me to download 20GB VM rather than trying to configure everything. Right now giving Docker another shot: https://developers.eos.io/eosio-nodeos/docs/docker-quickstart

  • 1
    Not sure if this is related but have you seen the jungle testnet? github.com/CryptoLions/EOS-Jungle-Testnet – Philip Kirkbride Jun 6 '18 at 16:12
  • 1
    @PhilipKirkbride look at the answer below - you are not the only one suggesting Crypto Lions... – Mars Robertson Jun 6 '18 at 16:45
  • 1
    Did you have a look at the Docker documentation on GitHub? Running it locally would be a simple "docker pull eosio/eos" and a "docker-compose up" – TeeAttack42 Jun 6 '18 at 17:52
  • 1
    It actually works! I didn't expect to be that easy... Producing my own blocks. Now onto first smart contract deployment... – Mars Robertson Jun 6 '18 at 21:36
  • 1
    @TeeAttack42 done... Silly me, it was super easy! – Mars Robertson Jun 8 '18 at 10:07
3

I cannot believe it was that easy.

My previous experience with Docker was terrible - error upon error, some configuration issues. I guess it was on the application level, not Docker level.

This time around - it just works! EOS running in 2 lines of code: https://developers.eos.io/eosio-nodeos/docs/docker-quickstart


  1. Pull the image from the repository:

docker pull eosio/eos-dev

  1. And start the EOSIO node:

sudo docker run --rm --name eosio -d -p 8888:8888 -p 9876:9876 -v /tmp/work:/work -v /tmp/eosio:/mnt/dev/data eosio/eos-dev /bin/bash -c "nodeos -e -p eosio --plugin eosio::wallet_api_plugin --plugin eosio::wallet_plugin --plugin eosio::producer_plugin --plugin eosio::history_plugin --plugin eosio::chain_api_plugin --plugin eosio::history_api_plugin --plugin eosio::http_plugin -d /mnt/dev/data --http-server-address=0.0.0.0:8888 --access-control-allow-origin=* --contracts-console"

  1. Check its working:

sudo docker logs --tail 10 eosio

0

actually there has not yet had an official testnet actually as declare at developer portal there is community testnet that you can try http://dev.cryptolions.io

  • I've had a look... need already installed EOS - it seems like installing EOS is required, the only thing is a testnet... Ouch! Now I see, my question wasn't precise enough... I mixed two concepts - seamless install and testnet. So now I know about testnet! – Mars Robertson Jun 6 '18 at 16:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for?Browse other questions tagged or ask your own question.