如何解决独立Docker容器间的连接问题？Node应用无法连接MongoDB与Elasticsearch求助

Hey there, let’s troubleshoot this connection issue step by step—since you’ve already tried setting up a Docker network, we can focus on the most common pitfalls that might still be blocking your Node app from reaching MongoDB and Elasticsearch.

First, confirm all three containers are actually attached to the same custom network (not Docker’s default bridge network, which has limited DNS resolution). Run these commands to verify:

• List all containers and their networks: docker ps --format "{{.Names}}: {{.Networks}}"
• Inspect your custom network to see attached containers: docker network inspect <your-network-name>

If any container is missing from the network, reattach it with: docker network connect <your-network-name> <container-name>

This is the #1 culprit for container connection issues. Never use localhost in your connection strings—each container has its own localhost, so your Node app is trying to connect to itself instead of the other containers.

Instead, use the container names (or service names if you switch to Compose) as the host:

• MongoDB connection string example: mongodb://<mongo-container-name>:27017/your-database-name
• Elasticsearch connection string example: http://<es-container-name>:9200

Double-check that you’re using the correct default ports: MongoDB uses 27017, Elasticsearch uses 9200. If you changed the internal port when running the container, update the string accordingly.

Even if containers are up, the underlying services might have failed to start. Let’s confirm:

• For MongoDB: Exec into the container and check if the service is listening:
  docker exec -it <mongo-container-name> netstat -tulpn | grep 27017
  You should see output showing it’s listening on 0.0.0.0:27017 (not just 127.0.0.1).
• For Elasticsearch: Exec into the container and test the local endpoint:
  docker exec -it <es-container-name> curl http://localhost:9200
  You should get a JSON response with Elasticsearch’s version info.

From your Node container, test if it can reach the other containers:

• Ping the MongoDB container by name: docker exec -it <node-container-name> ping <mongo-container-name>
• Ping the Elasticsearch container similarly.

If ping fails, there’s a DNS resolution issue in your Docker network. If ping works but connections still fail, check if the service ports are open or if there’s an authentication/permission issue (e.g., MongoDB requires credentials you haven’t added to the connection string).

Logs will tell you exactly what’s going wrong. Check each container’s logs:

• MongoDB logs: docker logs <mongo-container-name> (look for startup errors or authentication failures)
• Elasticsearch logs: docker logs <es-container-name> (common issues include memory limits or bootstrap checks failing)
• Node app logs: docker logs <node-container-name> (look for specific errors like ECONNREFUSED or ETIMEDOUT—these will point you to whether the issue is with reachability or service availability)

Manually running docker run commands can lead to typos or missed configuration. Docker Compose automates network setup, container dependencies, and environment variables. Here’s a basic example docker-compose.yml for your stack:

version: '3.8'
services:
  mongo:
    image: your-mongo-image-tag
    container_name: mongo-db
    networks:
      - app-network
  elasticsearch:
    image: your-es-image-tag
    container_name: es-service
    environment:
      - discovery.type=single-node
      - ES_JAVA_OPTS=-Xms512m -Xmx512m # Adjust memory if needed
    networks:
      - app-network
  node-app:
    image: your-node-image-tag
    container_name: node-service
    depends_on:
      - mongo
      - elasticsearch
    networks:
      - app-network

Run docker-compose up to start all services—this ensures they’re on the same network and start in the right order.

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