In this blog let’s learn how to create a bridge network. By definition – Bridge networks are usually used when your applications run in standalone containers that need to communicate<\/p>\n\n\n\n
A bridge network is a Link Layer device which forwards traffic between network segments.<\/p>docker.com<\/cite><\/blockquote>\n\n\n\n
When you create a network, Docker engine creates a non-overlapping sub-network for the network by default and for a bridge network you can only have one subnet.<\/p>\n\n\n\n
docker network<\/code><\/pre>\n\n\n\n
When you create a network, Engine creates a non-overlapping subnetwork for the network by default.<\/p><\/blockquote><\/figure>\n\n\n\n
Usage:\tdocker network COMMAND\n\nManage networks\n\nCommands:\n connect Connect a container to a network\n create Create a network\n disconnect Disconnect a container from a network\n inspect Display detailed information on one or more networks\n ls List networks\n prune Remove all unused networks\n rm Remove one or more networks\n\nRun 'docker network COMMAND --help' for more information on a command.<\/code><\/pre>\n\n\n\n
In terms of Docker, a bridge network uses a software bridge which allows containers connected to the same bridge network to communicate, while providing isolation from containers which are not connected to that bridge network.<\/p><\/blockquote><\/figure>\n\n\n\n
docker network create --help\n\nUsage:\tdocker network create [OPTIONS] NETWORK\n\nCreate a network\n\nOptions:\n --attachable Enable manual container attachment\n --aux-address map Auxiliary IPv4 or IPv6 addresses used by Network driver (default map[])\n --config-from string The network from which copying the configuration\n --config-only Create a configuration only network\n -d, --driver string Driver to manage the Network (default \"bridge\")\n --gateway strings IPv4 or IPv6 Gateway for the master subnet\n --ingress Create swarm routing-mesh network\n --internal Restrict external access to the network\n --ip-range strings Allocate container ip from a sub-range\n --ipam-driver string IP Address Management Driver (default \"default\")\n --ipam-opt map Set IPAM driver specific options (default map[])\n --ipv6 Enable IPv6 networking\n --label list Set metadata on a network\n -o, --opt map Set driver specific options (default map[])\n --scope string Control the network's scope\n --subnet strings Subnet in CIDR format that represents a network segment<\/code><\/pre>\n\n\n\n
The command above will allow to define a network my-nw<\/code> of type --driver bridge<\/code> for the containers to connect-to and use.<\/p>\n\n\n\n
docker network ls\nNETWORK ID NAME DRIVER SCOPE\na97c7c66f4fd bridge bridge local\nd39ea265c531 host host local\nefe4bfd141fe none null local\n69b302414233 my-nw bridge local<\/code><\/pre>\n\n\n\n
For a container to use this network one can specify the --network<\/code> option with the value my-nw<\/code> for it to utilize<\/p>\n\n\n\n
The Docker bridge driver automatically installs rules in the host machine so that containers on different bridge networks cannot communicate directly with each other.<\/p><\/blockquote><\/figure>\n\n\n\n
docker run --network my-nw --name using-nw samarthya\/mydummycontainer:1<\/code><\/pre>\n\n\n\n
Please note Bridge networks apply to containers running on the same<\/strong> Docker daemon host.<\/code><\/p>\n\n\n\n
When you create or remove a user-defined bridge or connect or disconnect a container from a user-defined bridge, Docker uses tools specific to the operating system to manage the underlying network infrastructure (such as adding or removing bridge devices or configuring iptables<\/code> rules on Linux).<\/p><\/blockquote><\/figure>\n\n\n\n
Learn by example In this blog let’s learn how to create a bridge network. By definition – Bridge networks are usually used when your applications run in standalone containers that need to communicate A bridge network is a Link Layer device which forwards traffic between network segments. docker.com When you create a network, Docker engine […]<\/p>\n","protected":false},"author":2,"featured_media":897,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"image","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[34],"tags":[82,91],"class_list":["post-892","post","type-post","status-publish","format-image","has-post-thumbnail","hentry","category-technical","tag-docker","tag-network","post_format-post-format-image"],"_links":{"self":[{"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/posts\/892","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/comments?post=892"}],"version-history":[{"count":0,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/posts\/892\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/media\/897"}],"wp:attachment":[{"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/media?parent=892"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/categories?post=892"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.samarthya.me\/wps\/wp-json\/wp\/v2\/tags?post=892"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}