Networking overview

Container networking refers to the ability for containers to connect to and communicate with each other, or to non-Docker workloads.

Containers have networking enabled by default, and they can make outgoing connections. A container has no information about what kind of network it's attached to, or whether their peers are also Docker workloads or not. A container only sees a network interface with an IP address, a gateway, a routing table, DNS services, and other networking details. That is, unless the container uses thenonenetwork driver.

This page describes networking from the point of view of the container, and the concepts around container networking. This page doesn't describe OS-specific details about how Docker networks work. For information about how Docker manipulatesiptablesrules on Linux, see Packet filtering and firewalls.

User-defined networks

You can create custom, user-defined networks, and connect multiple containers to the same network. Once connected to a user-defined network, containers can communicate with each other using container IP addresses or container names.

The following example creates a network using thebridgenetwork driver and running a container in the created network:

$docker network create -d bridge my-net
$docker run --network=my-net -itd --name=container3 busybox

Drivers

The following network drivers are available by default, and provide core networking functionality:

For more information about the different drivers, see Network drivers overview.

Container networks

In addition to user-defined networks, you can attach a container to another container's networking stack directly, using the--network container:<name|id>flag format.

The following flags aren't supported for containers using thecontainer: networking mode:

• --add-host
• --hostname
• --dns
• --dns-search
• --dns-option
• --mac-address
• --publish
• --publish-all
• --expose

The following example runs a Redis container, with Redis binding to localhost,then running theredis-clicommand and connecting to the Redis server over thelocalhostinterface.

$docker run -d --name redis example/redis --bind 127.0.0.1
$docker run --rm -it --network container:redis example/redis-cli -h 127.0.0.1

Published ports

By default, when you create or run a container usingdocker createordocker run, containers on bridge networks don't expose any ports to the outside world. Use the--publishor-pflag to make a port available to services outside the bridge network. This creates a firewall rule in the host, mapping a container port to a port on the Docker host to the outside world. Here are some examples:

Important

Publishing container ports is insecure by default. Meaning, when you publish a container's ports it becomes available not only to the Docker host, but to the outside world as well.

If you include the localhost IP address (127.0.0.1,or::1) with the publish flag, only the Docker host and its containers can access the published container port.

]\s+/gm, '')); copying = true; setTimeout(() => copying = false, 2000); ">

$docker run -p 127.0.0.1:8080:80 -p'[::1]:8080:80'nginx

Warning

Hosts within the same L2 segment (for example, hosts connected to the same network switch) can reach ports published to localhost. For more information, see moby/moby#45610

If you want to make a container accessible to other containers, it isn't necessary to publish the container's ports. You can enable inter-container communication by connecting the containers to the same network, usually a bridge network.

Ports on the host's IPv6 addresses will map to the container's IPv4 address if no host IP is given in a port mapping, the bridge network is IPv4-only, and--userland-proxy=true(default).

For more information about port mapping, including how to disable it and use direct routing to containers, see packet filtering and firewalls.

IP address and hostname

By default, the container gets an IP address for every Docker network it attaches to. A container receives an IP address out of the IP subnet of the network. The Docker daemon performs dynamic subnetting and IP address allocation for containers. Each network also has a default subnet mask and gateway.

You can connect a running container to multiple networks, either by passing the--networkflag multiple times when creating the container, or using thedocker network connectcommand for already running containers. In both cases, you can use the--ipor--ip6flags to specify the container's IP address on that particular network.

In the same way, a container's hostname defaults to be the container's ID in Docker. You can override the hostname using--hostname. When connecting to an existing network usingdocker network connect, you can use the--aliasflag to specify an additional network alias for the container on that network.

DNS services

Containers use the same DNS servers as the host by default, but you can override this with--dns.

By default, containers inherit the DNS settings as defined in the /etc/resolv.confconfiguration file. Containers that attach to the defaultbridgenetwork receive a copy of this file. Containers that attach to a custom network use Docker's embedded DNS server. The embedded DNS server forwards external DNS lookups to the DNS servers configured on the host.

You can configure DNS resolution on a per-container basis, using flags for the docker runordocker createcommand used to start the container. The following table describes the availabledocker runflags related to DNS configuration.

Custom hosts

Your container will have lines in/etc/hostswhich define the hostname of the container itself, as well aslocalhostand a few other common things. Custom hosts, defined in/etc/hostson the host machine, aren't inherited by containers. To pass additional hosts into a container, refer to add entries to container hosts filein the docker runreference documentation.

Proxy server

If your container needs to use a proxy server, see Use a proxy server.