Bridge Networking for Single Host Container Networking

Bridge Networking for Single Host Container Networking



This video demonstrates how to network containers on the same host using the bridge driver provided in Docker

Docker is an open platform for developers and system administrators to build, ship and run distributed applications. With Docker, IT organizations shrink application delivery from months to minutes, frictionlessly move workloads between data centers and the cloud and can achieve up to 20X greater efficiency in their use of computing resources. Inspired by an active community and by transparent, open source innovation, Docker containers have been downloaded more than 700 million times and Docker is used by millions of developers across thousands of the world’s most innovative organizations, including eBay, Baidu, the BBC, Goldman Sachs, Groupon, ING, Yelp, and Spotify. Docker’s rapid adoption has catalyzed an active ecosystem, resulting in more than 180,000 “Dockerized” applications, over 40 Docker-related startups and integration partnerships with AWS, Cloud Foundry, Google, IBM, Microsoft, OpenStack, Rackspace, Red Hat and VMware.

11 thoughts on “Bridge Networking for Single Host Container Networking

  1. Thanks for sharing your knowledge, would you please explain maybe in another video how to use ipv6 on docker networks? Once again thanks!

  2. Hi Nigel, could you explain a little bit on how this functions in a K8s cluster..? Since it is the control plane responsible for running container workloads, where does docker bridge enters the story?

  3. why do use root? i have the same issue with ubuntu.. after I install docker,i have to use sudo for
    the docker commands..

  4. Its good video for beginner. You triggered me to study more about Docker networking. Thank you very much

  5. This video pointed out something I did not know: Not specifying a network means the container gets attached to the default bridge. Not it is all making sense. Thanks!

Leave a Reply

Your email address will not be published. Required fields are marked *