-
Notifications
You must be signed in to change notification settings - Fork 662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while installing the indy-node package in docker pool setup #1848
Comments
The short version is here; #1846
If you are interested in getting this working, have a look at the Dockerfile referenced in the link to see how the installation process (and repositories) have changed. Other references you can use are the Dockerfiles for the dev container and git pod environments (which are basically the same).
Another example can be found here: |
Please feel free to contribute any fixes through a PR. |
The error message mentions the line RUN apt-get update -y && apt-get install -y indy-node libindy. This line is most likely located in the Dockerfile used to build the indycore image. Make sure this Dockerfile is present in the expected location within the indy-node repository you cloned. |
Closing this as resolved. |
I am following the indy-node docker pool setup to create the network on my Ubuntu 20.04.5 LTS machine.
Following this document - doc link
I git cloned the indy-node repo and after cloning
I changed to the following directory - indy-node/environment/docker/pool
And then used the command -
./pool_start.sh 4 10.0.0.2,10.0.0.3,10.0.0.4,10.0.0.5 10 9701
Now facing the error while building indycore attached in below image


Help me out with any solution or any new latest documentation or setups to run a indy network in my ubuntu machine.
The text was updated successfully, but these errors were encountered: