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".

  • How can I create a Docker image based on a git tag in the public Registry?
  • Docker registry on marathon insecure-registry
  • Using ARG command in a sub Dockerfile
  • How can I use the docker daemon from a container running on a host provisioned by Docker Machine?
  • Docker error: too many open files
  • Using Python 3 time.sleep in Raspberry Pi 3 hangs process
  • 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?

  • AWS Mesosphere: parameters for docker daemon
  • How to Setup Node & Docker on Windows 10 for Use with Bash on Ubuntu on Windows?
  • Docker remote api don't restart after my computer restart
  • Configuring kubectl against remote clusters
  • Error getting authority in Ubuntu SDK Docker image
  • connect robomongo to mongo instance running inside docker container
  • 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.