CODEWITHSUNDEEP
docker
Roland Pish
Roland Pish

Reputation: 815

Docker container cannot connect to linked containers services

I'm using Docker version 1.9.1 build a34a1d5 on an Ubuntu 14.04 server host and I have 4 containers: redis (based on alpine linux 3.2), mongodb (based on alpine linux 3.2), postgres (based on ubuntu 14.04) and the one that will run the application that connects to these other containers (based on alpine linux 3.2). All of the db containers expose their corresponding ports in the Dockerfile.

I did the modifications on the database containers so their services don't bind to the localhost IP but to all addresses. This way I would be able to connect to all of them from the app container. For the sake of testing, I first ran the database containers and then the app one with a command like the following:

docker run --rm --name app_container --link mongodb_container --link redis_container --link postgres_container  -t localhost:5000/app_image

I enter the terminal of the app container and I verify that its /etc/hosts file contains the IP and names of the other containers. Then I am able to ping all the db containers. But I cannot connect to their ports to any of the db containers.

A simple: telnet mongodb_container 27017 simply sits and waits forever, and the same happens if I try to connect to the other db containers. If I run the application, it also complains that it cannot connect to the specified db services.

Important note: I am able to telnet the corresponding ports of all the db containers from the host.

What might be happening?

EDIT: I'll include the run commands for the db containers:

docker run --rm --name mongodb_container -t localhost:5000/mongodb_image
docker run --rm --name redis_container -t localhost:5000/redis_image
docker run --rm --name postgres_container -t localhost:5000/postgres_image

Upvotes: 1

Views: 1219

Answers (1)

Roland Pish
Roland Pish

Reputation: 815

Well, the problem with telnet seems to be related to the telnet client on alpine linux since the following two commands showed me that the ports on the containers were open:

nmap -p27017 172.17.0.3
nc -vz 172.17.0.3 27017

Being focused mainly on the telnet command I issued, I believed that the problem was related to the ports being closed or something; and I overlooked the configuration file on the app that was being used to connect it to the services (it was the wrong filename), my bad.

All works fine now.

Upvotes: 2

Related Questions