2018-12-21 16:04

Docker出现“服务器选择超时错误” MongoDB Go驱动程序


I'm working on a very basic (I thought) starter program in Go using MongoDB and Docker. Trying to get a handle on these before we start using them at work. I've got my MongoDB running in a docker container, just using my local host, using the official Docker image. This is running fine, I can connect to it through MongoDB Compass and modify the DB.

My next task was to build a separate Docker container that is able to read and write to the DB. I'm using MongoDB-Go-Driver ( for this as mgo is no longer kept up.

This is my code, I'm just following the numerous tutorials online to make a simple connection and then ping the DB to ensure connectivity.

client, err := mongo.Connect("mongodb://localhost:27017")

if err != nil {
    log.Fatal("error ", err)

// Check the connection
err = client.Ping(context.TODO(), nil)

if err != nil {
    log.Fatal("error2 ", err)

fmt.Println("Connected to MongoDB!")

It always fails on doing any operation on the DB (Find, FindOne, Ping, etc.) with error2 server selection timeout

This is my docker-compose file I'm running.

version: "3"

    image: mongo
      - "27017:27017"
      - maccaptionNet
      - .:/go/src/maccaption_microservice/dbdata
    image: jobservicemaccaption:1.0
      - maccaptionNet
      - "datastore"

    driver: bridge

I'm brand new to MongoDB and after hours of research haven't made any progress on this. I've read through

Can anyone point me in the right direction for this? I haven't been able to find a lot on this specific issue.


  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享
  • 邀请回答


  • douzhang2092 douzhang2092 3年前

    When you running the service and mongodb in docker you can't use localhost since the service is in a different container than mongodb, and from docker point of view it's under a different ip address.

    You can connect with the service name you specify in docker-compose datastore




    By default Compose sets up a single network for your app. Each container for a service joins the default network and is both reachable by other containers on that network, and discoverable by them at a hostname identical to the container name

    Meaning that if you run multiple containers via compose, you can access one container from the other by the container name,

    Basically when docker-compose starts, it sets up the network, and each container in the compose joins the network under its container name. For a container's point if view, localhost is just the container itself, while he can search for other container's name and get back the container’s IP address.

    Assuming that the docker is running on your localhost, you can set the name in etc/hosts file like this: datastore

    (if not just replace with the docker ip)

    And in the app you will connect with mongodb://datastore:27017

    So you will be able to run the service both in the docker and from outside, if you'll decide to run only the db in docker

    docker-compose start datastore
    点赞 评论 复制链接分享
  • doujia1939 doujia1939 2年前

    Somehow i've fix this problem in a different way: by changing ports from "27018:27017" to "27017:27017". IDK why this helps. Maybe if Mongo sees not default port it thinks there are cluster of Mongo's nodes.

    点赞 评论 复制链接分享
  • dtzhfb4869 dtzhfb4869 3年前

    If you are connecting to one docker from another (like it is written in your docker-compose file, and using bridge network mode, you have to change your localhost to the hostname, like datastore

    client, err := mongo.Connect("mongodb://datastore:27017")

    When your go script uses localhost, it expects the database to located in the same docker

    点赞 评论 复制链接分享