求助：API及Mongo-Express容器无法通过Docker默认网络连接MongoDB

数据老陈

2026-5-19

Hey Marcos, let's figure out why your API and Mongo-Express containers can't connect to MongoDB. I've dealt with this exact kind of issue a bunch of times, so here's a step-by-step breakdown to fix it:

1. Verify Docker Network Setup

First off, containers need to be on the same network to talk to each other. Docker's default network can have DNS quirks, so a custom bridge network is way more reliable.

Check if your docker-compose.base.yml defines a shared network, and all services are attached to it:

# Add this at the bottom of your base config if it's missing
networks:
  app-network:
    driver: bridge

# Then update each service to join the network
services:
  mongodb:
    # ... other mongodb config
    networks:
      - app-network
  api:
    # ... other api config
    networks:
      - app-network
  mongo-express:
    # ... other mongo-express config
    networks:
      - app-network

2. Use Service Names Instead of localhost

This is the most common mistake! Containers can't reach MongoDB via localhost—that points to their own container, not the MongoDB one.

For your API, make sure the MongoDB connection string uses the service name (usually mongodb) as the host:
```
mongodb://mongodb:27017/your-database-name
```

For Mongo-Express, set the ME_CONFIG_MONGODB_SERVER environment variable to mongodb:

mongo-express:
  environment:
    ME_CONFIG_MONGODB_SERVER: mongodb
    ME_CONFIG_MONGODB_PORT: 27017
    # Add these if you've set auth on MongoDB
    ME_CONFIG_MONGODB_ADMINUSERNAME: root
    ME_CONFIG_MONGODB_ADMINPASSWORD: your-mongo-password

3. Check if MongoDB is Actually Running

Before blaming connections, confirm MongoDB is up and healthy:

Run docker ps to see if the MongoDB container is in the Up state. If it's restarting or exited, check its logs with:
```
docker logs <mongodb-container-name-or-id>
```
You can also test the MongoDB service directly by running:
```
docker exec -it <mongodb-container-name> mongosh
```

If you can connect here, the database itself is working—so the issue is definitely in cross-container communication.

4. Don't Forget Your Dev Config File

You're only using docker-compose.base.yml to start containers, but if docker-compose.dev.yml has critical settings (like network overrides or environment variables), you need to merge both files:

sudo docker-compose -f docker-compose.base.yml -f docker-compose.dev.yml up --abort-on-container-exit

Docker Compose applies config files in order, with later files overriding earlier ones—this ensures all your dev-specific settings are loaded.

5. Dig Into Container Logs for Specific Errors

If the above steps don't fix it, get granular with logs:

API container logs: docker logs <api-container-name> (look for connection timeout or auth errors)
Mongo-Express logs: docker logs <mongo-express-container-name> (it usually gives clear messages about why it can't reach MongoDB)

These logs will tell you exactly what's going wrong—whether it's a DNS issue, wrong credentials, or MongoDB not accepting connections.

内容的提问来源于stack exchange，提问作者Marcos J.C Kichel