You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 27, 2021. It is now read-only.
Hi,
I'm deploying a private network based on Hyperledger Besu.
I have 5 docker containers, one per node, running Besu (v 1.5).
Also, I have 5 docker container running ethstats-cli (last version at this moment), one per Besu node and some containers running ethstats network server, deepstream and dashboard.
Well, I have found this problem: If I try to run all these containers with docker compose, Network Statistics dashboard doesn't show all the data:
But, if I run all the dockers containers with a docker-compose file except ethstats-cli, and waits about 30 seconds, and then I run the ethstats-cli containers, then everything works properly.
I tried using depends_on instruction on docker-compose with no result. I think the issue is that if ethstat-client tries to connect with deepstream too early, the connection will never succeed.
Hi,
I'm deploying a private network based on Hyperledger Besu.
I have 5 docker containers, one per node, running Besu (v 1.5).
Also, I have 5 docker container running ethstats-cli (last version at this moment), one per Besu node and some containers running ethstats network server, deepstream and dashboard.
Well, I have found this problem: If I try to run all these containers with docker compose, Network Statistics dashboard doesn't show all the data:
But, if I run all the dockers containers with a docker-compose file except ethstats-cli, and waits about 30 seconds, and then I run the ethstats-cli containers, then everything works properly.
I tried using depends_on instruction on docker-compose with no result. I think the issue is that if ethstat-client tries to connect with deepstream too early, the connection will never succeed.
This is my docker-compose file:
The text was updated successfully, but these errors were encountered: