4
The set contract operation takes the account name as its first parameter (eosin.token in your example). If this account doesn't exist, if cannot set the contract. In your example above, you create a new account called myuser. You need to create an account called eosin.token in order to execute the set contract call you show.
4
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.
3
You can't install eosio using npm.
If you're looking for an alternative way to install & run a development environment using Docker you can follow the instructions for Docker-compose below. You can also choose a different build option altogether, I've added one below the Docker instructions:
git clone https://github.com/EOSIO/eos.git --recursive --...
3
The problem here was that the path provided was relative, and Rohan was working with a docker container. When passing the path to your contract's directory when using docker, it should be an absolute path, and match the mounted path of your docker container.
cleos set contract helocode1234 /contracts/hello helo.wasm helo.abi -p helocode1234@active
The ...
3
I would also recommend using the docker image from docker-hub.
Pull it by running the following command:
docker pull eosio/eos-dev
Now you create a folder in your local machine named Code
Afterwards you can start the container by running it with the following command. This will use your local Code folder and mount it to the filesystem in the docker ...
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
Pull the image from the repository:
...
2
It was due to corrupted images.
If you're using mac, you can resolve it by going to Preferences menu, click on Reset tab, and click "Remove all data." Then run docker pull eosio/eos-dev again.
2
If you do not have special reason to use your current docker image. It is better to use docker image included in eosjs. eosio.token contract is already deployed when running this docker.
https://github.com/EOSIO/eosjs/tree/master/docker
In addition, I recommend that building your own contract in your eos repository and copy result to the docker.
$ docker ...
2
Before deploying your contract, you should first compile it using eosiocpp tool.
If you haven't aliased eosiocpp yet, try running,
alias eosiocpp='docker exec eosio /opt/eosio/bin/eosiocpp'
Then cd to eosio.token folder, and there you can generate abi and wast file using the following commands,
eosiocpp -o eosio.token.wast eosio.token.cpp #for wast ...
1
Oh.. I'm so idiot.
https://developers.eos.io/eosio-nodeos/docs/docker
should be enough 7 GB memory.
1
This is what I could find on the discussion of moving from Docker; however, upon examining the release notes, I could find no elaboration of the rationale.
We're moving away from Docker images in favor of the pre-built
binaries. See https://github.com/EOSIO/eos/releases/latest and
https://github.com/EOSIO/eosio.cdt/releases/latest.
The only 2 ...
1
For the first issue, you could be exceeding the maximum CPU usage time allowed for a transaction. You can see below where this is hard coded:
const static uint32_t default_max_block_cpu_usage = 200'000; /// max block cpu usage in microseconds
const static uint32_t default_target_block_cpu_usage_pct = 10 * percent_1;
const ...
1
I was able to solve it by
~/scripts $ sudo service docker stop
[sudo] password for user:
~/scripts $ sudo service docker start
~/scripts $ ./docker_init.sh
docker: Error response from daemon: Conflict. The container name "/eosio" is already in use by container "a449dc043cd46b79775c239fc2c356637c888c704a4cf11299ae0d605d5a34b1". You have to remove (or ...
1
Your question is not clear. If you want to stop the node, simply remove the container using
docker rm -f eosio
command.
1
It is sufficient. As long as you have server powerful enough. Especially storage.
1
Maybe you will copy keosd from docker, and put it in the same directory of cleos.
When call cleos to interact with wallet, keosd will be launched by cleos.
1
The problem is due to the Docker Quickstart tutorial.
In short, the files are inside the Docker Container running the eosio instance.
To find the files inside the docker do the following:
Find the path to the wallet:
There might be better ways to do that, but the way I did was reading eosio logs running in one terminal docker logs --tail 10 eosio -f ...
1
You want to add the --filter-on switch against the account/action you want to capture when running nodeos
E.g.
--filter-on ${Contract}:${Action}
--filter-on karmaaccount:createpost:
Full example
nodeos -e -p eosio -d /mnt/dev/data --config-dir /mnt/dev/config --http-validate-host=false --plugin eosio::wallet_api_plugin --plugin eosio::wallet_plugin --...
1
You can start nodeos with this command, your plugin comes in bolded area.
docker run --rm --name eosio -d -p 8888:8888 -p 9876:9876 -v
/tmp/work:/work -v /tmp/eosio/data:/mnt/dev/data -v
/tmp/eosio/config:/mnt/dev/config eosio/eos-dev /bin/bash -c "nodeos
-e -p eosio --plugin eosio::wallet_api_plugin --plugin eosio::wallet_plugin --plugin eosio::...
1
Two suggestions:
1) Try to run it with admin privileges
sudo docker pull ...
2) If that still fails, clean your docker images/volumes/containers. Afterwards you can try the production image. With
sudo docker pull eosio/eos
Edit:
Seems that your docker daemon is not running.
Try to run
dockerd
Maybe use some of the answers from this link
1
I've been using Docker lately for several reasons.
Advantages
Easier than a VM by just running a couple of commands
I can segregate my host node, keosd and cleos node on 3 different instances in 3 seconds.
Starting from scratch is a matter of rebooting.
Debugging or sending my environment to another person might prove useful than working out how to cart ...
1
Maybe try to pull the image from Docker Hub:
https://hub.docker.com/r/eosio/eos/
If you have correctly installed docker
sudo docker pull eosio/eos
Should be enough...
Be sure to maintain your images so that you don't try to start your local built image.
EDIT
From the Quickstart Guide.
If you want to start it use:
sudo docker run --rm --name eosio -d ...
Only top voted, non community-wiki answers of a minimum length are eligible
