执行./startFabric.sh遇daemon错误及容器未运行问题求解决方案

Got it, let's work through this issue step by step. That error message tells us one of your Hyperledger Fabric containers failed to start up properly, even after the script waited 15 seconds. Here's how to diagnose and fix it:

1. First, Get the Exact Failure Reason from Container Logs #

The error gives you a container ID (e7e73f14680e75372fe535dd6af95a88af2e6a704afd0ad69671ea0ec4a00922), so let's pull its logs to see why it crashed:

docker logs e7e73f14680e75372fe535dd6af95a88af2e6a704afd0ad69671ea0ec4a00922

This will show you specific errors like port conflicts, missing dependencies, or resource limits—this is the most critical step to pinpoint the root cause.

2. Fix Common Culprits #

Based on typical Fabric startup issues, here are the most likely fixes:

Port Conflict #

Fabric containers use default ports (e.g., 7050, 7051, 7053). If another program is using these ports, the container can't start:

• On Linux/macOS, check for port usage:

  netstat -tulpn | grep 7050  # Replace 7050 with the port mentioned in logs
  

• On Windows:

  netstat -ano | findstr 7050
  

Stop the program using the port, or modify your Fabric configuration files to use alternative ports.

Insufficient Docker Resources #

Fabric needs enough memory to run—at least 2GB, but 4GB is recommended. If Docker is starved for resources:

1. Open Docker Desktop settings
2. Go to Resources > Advanced
3. Increase the memory allocation (e.g., to 4GB) and apply changes
4. Restart Docker and re-run ./startFabric.sh

Corrupted or Mismatched Fabric Images #

Sometimes local images get corrupted or don't match the version your script expects. Clean up old resources and re-pull:

# Stop all running containers
docker stop $(docker ps -aq)
# Delete all stopped containers
docker rm $(docker ps -aq)
# Delete Hyperledger Fabric images
docker rmi $(docker images | grep hyperledger | awk '{print $3}')

Now re-run ./startFabric.sh—the script will automatically pull the correct fresh images.

Outdated Docker/Docker Compose #

Old Docker versions can cause compatibility issues with Fabric. Check your versions:

docker --version
docker-compose --version

Update to the latest stable versions of Docker and Docker Compose, then restart your system and try again.

3. Test Manual Container Startup #

If the logs point to a specific service issue, try starting the container manually using the same parameters from startFabric.sh (or the associated docker-compose.yaml file). This will give you real-time error output to debug further.

内容的提问来源于stack exchange，提问作者user8595144