ava-labs
lack of information about docker container
Hello,
The infos about the docker on the README.md is lacking important informations.
It should mention to map a volume like so:
docker run -ti -p 9650:9650 -p 9651:9651 -v /host/avalanche:/root/.avalanchego avalanchego-xxxxxxxx /avalanchego/build/avalanchego --network-id=local --staking-enabled=false --snow-sample-size=1 --snow-quorum-size=1
If not set when removing the container eg. for an update. the stacker.crt and stacker.key will be removed so the NodeId will be reseted.
Also would love to see more docker support here. I can't seem to figure out how to call the API with outside of the docker container. It looks like port 9650 should be exposed right?
@PatrickAlphaC thanks for raising this issue. Our docker support definitely needs some work, so I'll try to fix this ASAP.
As for sending API requests to the docker container, you will have to start it with the command line parameter --http-host= . This is the same as if you wanted to publicly expose the http API port.
Yes, your comment on https://github.com/ava-labs/avalanchego/issues/453 helped a lot.
Looks like the README.md needs to be updated again.
The docker image is now avaplatform/avalanchego and you run the node with
docker run -ti -p 9650:9650 -p 9651:9651 avaplatform/avalanchego /avalanchego/build/avalanchego --network-id=fuji --http-host=
It looks like the avalanchego-xxxxxx has been removed.
FYI, I think this syntax is much nicer :)
I'm trying to get a Docker-compose file to use the Avalanche Docker image and am running into a few issues.
The file is below https://github.com/pangolin-community/subgraph/blob/master/docker-compose.yaml
But I haven't figured out how to add the command line arguments to the docker-compose file. Any tips on what I should be attempting?
I checked avalanchego docker file https://github.com/ava-labs/avalanchego/blob/master/Dockerfile ... does it have any volumes at all? When I ran it and study with docker inspect it's not working. Obviously it's made for short term testing? I would consider current Dockerfile as a bug.
