[StackOverflow/docker] Deploying chaincode failed, socket is broken

### ROOT CAUSE The issue arises due to a Docker networking problem during Hyperledger Fabric chaincode deployment. The error "socket is broken" typically occurs when the peer node fails to establish a connection with the ordering service or other network components. This can stem from: 1. **Network misconfiguration**: Incorrect Docker bridge settings or firewall rules blocking inter-container communication. 2. **Resource constraints**: Insufficient memory or CPU on the host machine, affecting Docker networking. 3. **Version mismatches**: Incompatible Docker/Fabric versions leading to protocol conflicts. 4. **TLS/Security issues**: Misconfigured certificates or encryption causing handshake failures. ### CODE FIX 1. **Verify Docker Network**: ```bash # Check if containers are on the same bridge docker network inspect bridge # Create a custom bridge if needed docker network create --driver bridge fabric-network docker container connect fabric-network ``` 2. **Check Resource Limits**: ```bash # Monitor system resources docker stats # Increase memory limit in Docker daemon.json (if needed) sudo nano /etc/docker/daemon.json # Add: {"max-container-mem": "512m"} ``` 3. **Update Docker/Fabric**: ```bash # Check versions docker version peer version # Upgrade if necessary sudo apt-get install docker-ce= peer= ``` 4. **Validate TLS Certificates**: ```bash # Inspect chaincode container logs docker logs | grep -i "TLS" # Re-generate certificates if expired cryptogen generate --output ./crypto-config ``` 5. **Debugging**: ```bash # Check peer connectivity to orderer docker exec nc -zv orderer.example.com 7050 # Rebuild chaincode with debug mode docker build --build-arg DEBUG=1 -t chaincode:debug . ``` **Note**: Replace `` with actual container IDs and adjust paths/parameters based on your environment.