Dockerized Cyberd Node.
Differences between this and the original version https://github.com/cybercongress/cyberd/
- Processes managed via supervisor for logging and autorestart
- Repository is cloned during build process rather than copied into the build process
- Docker
- Docker-Compose (optional)
TK
TK
TK
TK
The following command will build the image.
docker build --rm -f Dockerfile -t docker-cyberd:latest .
docker-compose up -d --build
The image uses Supervisor to run both cyberd and cyberdcli simultaneously at container runtime. Supervisor also restarts either process should it fail for some reason.
After starting the container you can check the status here: http://127.0.0.1:26657/status.
or from the terminal
curl -X GET \
http://127.0.0.1:26657/status? \
-H 'cache-control: no-cache'
Supervisor starts the rest-server with the following command:
cyberdcli rest-server --trust-node --chain-id=euler-5 --laddr=tcp://0.0.0.0:1317 --indent --home=/root/.cyberdcli
You can verify that the rest-server is running using the following example
curl -X GET \
http://127.0.0.1:1317/blocks/latest \
-H 'cache-control: no-cache'