You must connect containers with the –link option in your docker run command.
Docker does not support automatic service discovery on bridge. If you have containers running on your network, docker network inspect displays networking information for your containers.Īny containers on the same network may communicate with one another via IP addresses. # docker network inspect bridgeĭocker automatically creates a subnet and gateway for the bridge network, and docker run automatically adds containers to it. When you run the following command in your console, Docker returns a JSON object describing the bridge network. Run ifconfig on the Linux host to view the bridge network. If you create a new network test_docker_nw, you can connect your container (test_container) with: # docker run test_container -net=test_docker_nwĪll Docker installations represent the docker0 network with bridge Docker connects to bridge by default. Specify which network a container should use with the –net flag. To get further details on networks, run: # docker network inspectĭocker creates three networks automatically on install: bridge, none, and host. To view Docker networks, run: # docker network ls We will have a closer look at each of those modes relevant for a single-host setup and conclude at the end of this article with some general topics such as security. In a nutshell, there are four modes available for Docker networking: bridge mode, host mode, container mode, or no networking. Docker networking is the native container SDN solution you have at your disposal when working with Docker.
0 kommentar(er)
