Docker – Not able to telnet Linked Container

I have a container A with Dockerfile as follows:

FROM ubuntu:latest
MAINTAINER arpitaggarwal ""

and another container B with Dockerfile as follows:

  • How to run multiple Docker Containers in different terminals using Docker compose or with Shell?
  • How docker treats fsync on guest filesystem? Is it possible to lost data during host system crash?
  • How to version control Docker containers' data volumes?
  • How to detect if docker run succeeded programmatically?
  • celery won't connect to rabbitmq broker for kubernetes
  • Issue with docker Inter container communication on the isolated bridge
  • ...
    FROM ubuntu:latest
    MAINTAINER arpitaggarwal ""
    RUN apt-get install -q -y mysql-server
    EXPOSE 3306

    Then I started the container B using command:

    docker run -P -it --name db B /bin/bash

    And running the command: docker run --rm --name web --link db A env

    gives me below output:


    Then I logged into container A and run the command: ping db

    which gives me output:

    PING db ( 56(84) bytes of data.
    64 bytes from db ( icmp_seq=1 ttl=64 time=0.082 ms
    64 bytes from db ( icmp_seq=2 ttl=64 time=0.063 ms
    64 bytes from db ( icmp_seq=3 ttl=64 time=0.065 ms
    64 bytes from db ( icmp_seq=4 ttl=64 time=0.061 ms
    64 bytes from db ( icmp_seq=5 ttl=64 time=0.066 ms

    And when I tried telnet command with port 3306, as follows:

    telnet 3306

    gives me output:

    root@9b078c1fed82:/# telnet 3306
    telnet: Unable to connect to remote host: Connection refused

    Any idea, how can I telnet linked container?

    Any help will be appreciated!

  • build Docker images from GitLab
  • unable to import large database to docker mysql container
  • Docker attach delay
  • docker run image causes syntax error /bin/sh
  • How do you use docker-compose from a Gitlab Registry on DigitalOcean?
  • Elasticsearch 2.0.0 cluster zen discovery in docker
  • 2 Solutions collect form web for “Docker – Not able to telnet Linked Container”

    MySQL usually only listens on by default. You need to modify the my.cnf during build and set bind-address to You could accomplish this with something like:

    RUN sed -i -e"s/^bind-address\s*=\s* =" /etc/mysql/my.cnf

    After receiving the answer by @Andy Shinn, I Updated the container B Dockerfile as below:

    FROM ubuntu:latest
    MAINTAINER arpitaggarwal ""
    RUN apt-get install -q -y mysql-server
    RUN apt-get install -q -y mysql-client
    RUN sed -i -e"s/^bind-address\s*=\s* =" /etc/mysql/my.cnf
    EXPOSE 3306

    And when I tried accessing mysql-server from container A as:

    mysql -u root -ppassword -h

    Gives me error:

    ERROR 1130 (HY000): Host '' is not allowed to connect to this MySQL server

    Which I figured it out is because container A was trying to connect to db container through root user. But In mysql do not allow you to connect though root user remotely. So I work around creating another user in mysql-server with root privileges.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.