Closed benjsmi closed 6 years ago
Specifically, it seems like the problem occurs when the third node tries to join the network.
Connecting node 1 to node 2 works fine if I run them manually from the prompt using docker flags. Then when the third joins, it causes the first two to barf.
Thanks for the info @benjsmi, the issue occurred when we stopped using a python virtual environment because a change to the pipenv
utility changed and broke the build. (venv should be unnecessary in a docker container anyways). It seemed to be an issue with indy-plenum.
I never figured out what the issue was but reverting to using a virtual environment with a work-around for the pipenv change has fixed the build for now.
Let me know if the build still does not work for you.
Thanks!
Running this as is on an Ubuntu machine using Docker compose, here's the logs for Node1:
My environment:
Linux kernel info:
Docker-compose info:
Docker info: