-
Notifications
You must be signed in to change notification settings - Fork 312
Failed to run on docker #4174
Comments
Is there any issue caused by this error message? Overall this is caused by two nodes trying to establish connection while already being connected. From what I know this should not cause any issues and the error in the logs is just an indication of that condition. Could you please confirm. |
@maciejzaleski I see the below one with the 46 of 46 block producers hit. However, I don't see the balance getting updated. Any help would be appreciated. |
Interesting wordage... "he". Are we assuming the "miner" is a biological entity ? 🤔 I'm all into A.I., but it will always be an "it" 😆 |
I managed to reproduce the error with Here are the steps which should get you back into the right tracks: Make sure that you are using the correct docker-compose file from here: Remove old containers and their data: Ensure that you have the latest docker images: Start it up again: You should get the pre-mine reward into Node_1 wallet at second block. |
@maciejzaleski Thanks a lot for resolving the issue. I just followed your steps and was able to see the balance on Node_1 wallet. |
Failing to run on docker.
docker pull stratisgroupltd/blockchaincovid19:latest
docker-compose -f 3-NodeNetwork.yml up
The text was updated successfully, but these errors were encountered: