Docker network – Why docker container responds on 127.0.0.1?

I start up a docker container with a service that runs on port 9324:

docker run -d -p 9324:9324 vsouza/sqs-local

I imagine that this container will run o bridge0 network. So If I run: docker network inspect bridge, I can see that this container is on ip: "IPv4Address": "172.17.0.2/16".

  • $(pwd) - one level up
  • Docker container for Laravel: PHP 7.x on CentOS 7.x
  • Docker seems to have no tty?
  • Kafka log directories in Docker
  • Copy Docker container from boot2docker under OS X
  • click-and-run docker image (or VM) with web interface?
  • The service is responding on both ip: 172.17.0.2:9324 and 127.0.0.1:9324.

    Why this service is responding on 127.0.0.1?

  • Cannot hit docker container running locally
  • I can't set up Kubernetes in Centos 7: Unable to update cni config
  • Docker Service Separation
  • docker windows exposed ports cannot be accessed from outside the host
  • ERROR: The Docker Engine version is less than the minimum required by Compose
  • Docker ERROR: Container command not found or does not exist when running from Win10
  • One Solution collect form web for “Docker network – Why docker container responds on 127.0.0.1?”

    The -p 9324:9324 tells docker to publish the 9324 port in the container on the host at port 9324. The actual mechanics of that are with some iptables rules to do a masquerade and a dnat on that port (for outbound and inbound traffic respectively). This is frequently done since you don’t always know the ip of each container, and may have your firewall rules configured to block direct access to the container (which you don’t in your environment).

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