Hyperledger Fabric Setup Issues and Docker Container Communication: Error in instantiating ledger provider: Get "http://couchdb0:5984/": dial tcp 172.19.0.6:5984: i/o timeout http error calling couchdb

General
,
1

Hello Community,

I hope this message finds you well. We’ve been facing some challenges while setting up Hyperledger Fabric under the same network, and we’re reaching out to seek your expertise and guidance.

Issue: Hyperledger Fabric Setup We attempted to set up Hyperledger Fabric under the same network, but encountered a problem with the containers for PEERs. The containers were getting exited, and upon checking the logs, we found the following error:

panic: Error in instantiating ledger provider: Get "http://couchdb0:5984/": dial tcp 172.19.0.6:5984: i/o timeout http error calling couchdb

We would appreciate any insights or suggestions on how to resolve this issue. If anyone has encountered a similar problem or has expertise in Hyperledger Fabric, your assistance would be invaluable.

As a workaround, we tried setting up an example application for communication between two containers under the same network. We followed the steps outlined in this tutorial: Connecting Two Docker Containers Over the Same Network. But messages sent by Container 1 was not captured by Container2.

If anyone has experience with this or has insights into Docker container communication, we’d love to hear your thoughts. The goal is to establish a reliable communication channel between containers, and we’re open to any suggestions or alternative methods that have worked for you.

Your expertise is crucial in helping us overcome these challenges, and we look forward to your valuable input.

2

How about you share your docker-compose.yml file(s), so we can understand your setup and apply our expertise? :slightly_smiling_face:

3

Hello Community,

Thank you for your engagement and insights. After a thorough investigation, we’ve identified the root cause of the issue. It appears that the use of the instance with CIS Ubuntu Level 1 image, which follows strict security norms and hardening measures, is affecting the communication between Hyperledger Fabric Peer containers and the CouchDB container. This issue is not only with Hyperledger Fabric, but you will face issue with normal docker applications as well e.g: Connecting Two Docker Containers Over the Same Network - GeeksforGeeks

For users encountering similar challenges with CIS Ubuntu images, it is crucial to explicitly expose Docker to IP tables and NF tables. This step is necessary to ensure proper communication and prevent issues related to connectivity.

Also, make sure to restart the instance once docker is exposed as it would have any effects until the instance restarted.