Cannot connect to remote Database instance from my docker container, however can connect from my host computer

Question

I have a problem connecting to remote database instances from a docker container.

I have a Docker container with a simple piece of Python code that connects to a remote MongoDB instance

    client = MongoClient('mongodb-example_conn_string.com')
    db = client.test_db
    collection = db.test_collection
    print(collection.find_one())

I can run this piece of code from my host machine (a laptop running Linux Mint 20) and it prints the result as expected.

When I build a Docker image (python:3.6.10-alpine) for this script and Docker Run then image I get an error message. The Container is running on the host laptop.

e.g.

docker build . -t py_connection_test
docker run --rm py_connection_test run

I get this error

pymongo.errors.ServerSelectionTimeoutError: mongodb-example_conn_string.com:27017: [Errno -2] Name does not resolve, Timeout: 30s, Topology Description: <TopologyDescription id: 60106f40288b81e007fe75a8, topology_type: Single, servers: [<ServerDescription ('mongodb-example_conn_string.com', 27017) server_type: Unknown, rtt: None, error=AutoReconnect('mongodb-example_conn_string.com:27017: [Errno -2] Name does not resolve',)>]>

The MongoDB remote instance is an internal database at work and a VPN (Using OpenVPN) is required to access it. I’ve used traceroute on host machine and docker container to confirm that network traffic is routed through the VPN, all seems to be fine there.

I’ve tried Docker Run with flag

--network="host"

But the same thing happens

I’m scratching my head at this, why does the same connection url not working in both cases? Is there something simple I’ve missed?

Asked By: ryansusername

||

Source

Answer 1

I’ve figured out the issue, thanks to Max for pointing me to look into DNS.

My problem was a faulty /etc/resolv.conf file on my host machine that the Docker Container was picking up. It contained 2 nameserver entries

In my case I could create the file /etc/docker/daemon.json on my host and add my dns entry there for the Container to pickup when run. e.g. adding lines:

{
     "dns": ["172.31.0.2"]
}

Editing / creating this file requires a Docker service restart

I got some helpful hints from https://l-lin.github.io/post/2018/2018-09-03-docker_ubuntu_18_dns/

Answered By: ryansusername

Answer 2

If you are not using DNS to specify the connection but are using a VPN to reach the resource and run into this issue it is most likely to be related to a docker network covering the IP range of your VPN, see this github issue for more details.

For a temporary solution, try docker network prune, if that does not help try killing all containers then pruning and if that does not help then either try a full docker restart than prune or the next step.

For a permanent solution (or at least more longlasting) check this guide (it will require restarting the Docker Daemon).

Answered By: Guilherme Z. Santos

Cannot connect to remote Database instance from my docker container, however can connect from my host computer

Question:

Answers: