$ sudo docker inspect --format '{{.State.Pid}}' docker1\n2094\n$ sudo ln -s \/proc\/2094\/ns\/net \/var\/run\/netns\/ns-2094<\/pre>\nThen we may use ip netns command to extract the network information<\/p>\n
$ sudo ip netns\nns-2094 (id: 0)\n$ sudo ip netns exec ns-2094 ip link\n1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT qlen 1\n link\/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\n11: eth0@if12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT\n link\/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0<\/pre>\nHere we go. The interesting information is the container network interface 11:<\/strong> eth0@if12<\/strong><\/p>\nSo, the first pair is the eth0 interface on the Docker container and the \u201coutside\u201d pair corresponds to the interface number 12. On the host the interface 12 corresponds to the virtual ethernet adapter veth45297ff. Note we may also find out the pair corresponding to the container interface (@if11).<\/p>\n
$ ip a | grep \"^12\"\n12: veth45297ff@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP<\/pre>\nFinally, let\u2019s take a look at the bridge used by the virtual ethernet adapter veth45297ff<\/p>\n
$ sudo brctl show\nbridge name bridge id STP enabled interfaces\ndocker0 8000.02422ad07e76 no veth45297ff\n veth46a8316<\/pre>\nThe other veth (46a8316) corresponds to my second docker2 container.<\/p>\n
\n- User-defined network bridges<\/strong><\/li>\n<\/ul>\n
But as said previously using the Docker0 bridge is only suitable for very limited scenarios. User-defined bridges are more prevalent with more complex scenarios like microservice applications because they offer a better isolation between containers and the outside world as well as a better manageability and customization. At this stage we may also introduce macvlan networks but probably in the next blog post \u2026<\/p>\n
For example, let\u2019s say you want to create 2 isolated network bridges for a 3-tiers application. The users will access the web server (from the exposed port) throughout the first network (frontend-server). But in the same time, you also want to prevent containers that sit on this network to make connections to the outside world. The second network (backend-server) will host containers that must have access to both the outside SQL Server database and the web server.<\/p>\n
![\"blog](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-5-docker-network-bridge-segregation-e1518611126838.jpg\")
<\/p>\n
User-defined networks is a good solution to address these requirements. Let\u2019s create two user-defined networks. Note by default containers may make connections to the outside world but the outside is not able to make connections to the containers without exposing listen ports. This is why I disabled ip masquerading<\/strong> (com.docker.network.bridge.enable_ip_masquerade=false<\/strong>) for the frontend-server network to meet the above requirements.<\/p>\n$sudo docker network create \\\n --driver bridge \\\n --subnet 172.20.0.0\/16 \\\n --gateway 172.20.0.1 \\\n backend-server \n$sudo docker network create \\\n --driver bridge \\\n --subnet 172.19.0.0\/16 \\\n --gateway 172.19.0.1 \\\n --opt com.docker.network.bridge.enable_ip_masquerade=false \\\n frontend-server\n$ sudo docker network ls \nNETWORK ID NAME DRIVER SCOPE\n5c6f48269d2b backend-server bridge local\n985f25500e3d bridge bridge local\nb1fbde4f4674 frontend-server bridge local\nad52b859e3f9 host host local\n1beda56f93d3 none null local<\/pre>\nLet\u2019s now take a look at the corresponding iptables masquerading rules on my host machine:<\/p>\n
$ sudo iptables -t nat -L -n | grep -i \"masquerade\"\nMASQUERADE all -- 172.20.0.0\/16 0.0.0.0\/0\nMASQUERADE all -- 172.17.0.0\/16 0.0.0.0\/0<\/pre>\nYou may notice only the Docker0 (172.17.0.0\/16) and backend-server (172.20.0.0\/16) bridges are allowed for ip masquerading.<\/p>\n
Then let\u2019s create 2 containers with the two first ones (docker1 and docker2) that will sit on the frontend-server network and the second one (docker2) on the backend-server network. For convenient purposes, I setup fixed hostnames for each container. I also used a different ubuntu image that provides this time all necessary network tools including ping command.<\/p>\n
$ sudo docker run -d --rm --name=docker1 --hostname=docker1 --net=frontend-server -it smakam\/myubuntu:v6 bash\n\n$ sudo docker run -d --rm --name=docker2 --hostname=docker2 --net=frontend-server -it smakam\/myubuntu:v6 bash\n\n$sudo docker run -d --rm --name=docker3 --hostname=docker3 --net=backend-server -it smakam\/myubuntu:v6 bash\n\n$ sudo docker ps\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES\n225ee13c38f7 smakam\/myubuntu:v6 \"bash\" 2 minutes ago Up 2 minutes docker3\nd95014602fe2 smakam\/myubuntu:v6 \"bash\" 4 minutes ago Up 4 minutes docker2\n1d9645f61245 smakam\/myubuntu:v6 \"bash\" 4 minutes ago Up 4 minutes docker1<\/pre>\nFirst, probably one of the biggest advantages of using user-defined networks (unlike Docker0 bridge) is the ability to use automatic DNS resolution between containers on the same user-defined subnet on the same host (this is default behavior but you can override DNS settings by specifying –dns<\/strong> parameter at the container creation time). In fact, Docker applies update on the \/etc\/hosts file of each container when adding \/ deleting containers.<\/p>\nAs expected, I may ping docker2 container from docker1 container and vice-versa but the same doesn\u2019t apply between neither docker1 and docker3 nor docker2 and docker3 because they are not sitting on the same network bridge.<\/p>\n
$ sudo docker exec -ti docker1 ping -c2 docker2\nPING docker2 (172.19.0.3) 56(84) bytes of data.\n64 bytes from docker2.frontend-server (172.19.0.3): icmp_seq=1 ttl=64 time=0.088 ms\n64 bytes from docker2.frontend-server (172.19.0.3): icmp_seq=2 ttl=64 time=0.058 ms\n\u2026\n$ sudo docker exec -ti docker2 ping -c2 docker1\nPING docker1 (172.19.0.2) 56(84) bytes of data.\n64 bytes from docker1.frontend-server (172.19.0.2): icmp_seq=1 ttl=64 time=0.084 ms\n64 bytes from docker1.frontend-server (172.19.0.2): icmp_seq=2 ttl=64 time=0.054 ms\n...\n$ sudo docker exec -ti docker1 ping -c2 docker3\nping: unknown host docker3\n...\n\n<\/pre>\nFrom a network perspective, on the host we may notice the creation of two additional bridge interfaces and 3 virtual Ethernet adapters after the creation of the containers.<\/p>\n
$ brctl show\nbridge name bridge id STP enabled interfaces\nbr-5c6f48269d2b 8000.0242ddad1660 no veth79ae355\nbr-b1fbde4f4674 8000.02424bebccdd no vethb66deb8\n vethbf4ab2d\ndocker0 8000.02422ad07e76 no\n$ ip a | egrep \"^[1-9][1-9]\"\n25: br-5c6f48269d2b: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP\n28: br-b1fbde4f4674: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP\n58: vethb66deb8@if57: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-b1fbde4f4674 state UP\n64: veth79ae355@if63: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-5c6f48269d2b state UP<\/pre>\nIf I want to make the docker3 container reachable from docker2 container I may simply connect the latter to the corresponding network as shown below:<\/p>\n
$ sudo docker network connect backend-server docker2\n\n$ sudo docker inspect docker2\n[\n\"Networks\": {\n \"backend-server\": {\n \"IPAMConfig\": {},\n \"Links\": null,\n \"Aliases\": [\n \"d95014602fe2\"\n ],\n \"NetworkID\": \"5c6f48269d2b752bf1f43efb94437957359c6a72675380c16e11b2f8c4ecaaa1\",\n \"EndpointID\": \"4daef42782b22832fc98485c27a0f117db5720e11d806ab8d8cf83e844ca6b81\",\n \"Gateway\": \"172.20.0.1\",\n \"IPAddress\": \"172.20.0.3\",\n \"IPPrefixLen\": 16,\n \"IPv6Gateway\": \"\",\n \"GlobalIPv6Address\": \"\",\n \"GlobalIPv6PrefixLen\": 0,\n \"MacAddress\": \"02:42:ac:14:00:03\",\n \"DriverOpts\": null\n },\n \"frontend-server\": {\n \"IPAMConfig\": null,\n \"Links\": null,\n \"Aliases\": [\n \"d95014602fe2\"\n ],\n \"NetworkID\": \"b1fbde4f4674386a0e01b7ccdee64ed8b08bd8505cd7f0021487d32951035570\",\n \"EndpointID\": \"651ad7eaad994a06658941cda7e51068a459722c6d10850a4b546382c44fff86\",\n \"Gateway\": \"172.19.0.1\",\n \"IPAddress\": \"172.19.0.3\",\n \"IPPrefixLen\": 16,\n \"IPv6Gateway\": \"\",\n \"GlobalIPv6Address\": \"\",\n \"GlobalIPv6PrefixLen\": 0,\n \"MacAddress\": \"02:42:ac:13:00:03\",\n \"DriverOpts\": null\n }\n }\n]<\/pre>\nYou may notice the container is connected to the frontend-server and backend-server as well thanks to an additional network interface created at same time.<\/p>\n
$ sudo docker exec -it docker2 ip a show | grep eth\n59: eth0@if60: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default\n link\/ether 02:42:ac:13:00:03 brd ff:ff:ff:ff:ff:ff\n inet 172.19.0.3\/16 brd 172.19.255.255 scope global eth0\n68: eth2@if69: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default\n link\/ether 02:42:ac:14:00:03 brd ff:ff:ff:ff:ff:ff\n inet 172.20.0.3\/16 brd 172.20.255.255 scope global eth2<\/pre>\nPinging both docker1 container and docker3 container from docker2 container is successful now.<\/p>\n
$ sudo docker exec -it docker2 ping -c2 docker1\nPING docker1 (172.19.0.2) 56(84) bytes of data.\n64 bytes from docker1.frontend-server (172.19.0.2): icmp_seq=1 ttl=64 time=0.053 ms\n64 bytes from docker1.frontend-server (172.19.0.2): icmp_seq=2 ttl=64 time=0.052 ms\n\u2026\n$ sudo docker exec -it docker2 ping -c2 docker3\nPING docker3 (172.20.0.2) 56(84) bytes of data.\n64 bytes from docker3.backend-server (172.20.0.2): icmp_seq=1 ttl=64 time=0.082 ms\n64 bytes from docker3.backend-server (172.20.0.2): icmp_seq=2 ttl=64 time=0.054 ms\n\u2026<\/pre>\nIn this blog post, we surfaced Docker network bridges and use cases we may have to deal with SQL Server instances regarding the context. As a reminder, user-defined networks may allow to define fine-grained policy rules to interconnect containers on different subnets. This is basically what we may want to achieve with microservices applications. Indeed, such applications include some components that need to span multiple networks (backend and frontend networks) whereas other ones should by isolated (even from outside) regarding their role.<\/p>\n
Happy containerization!<\/p>\n
By David Barbarin<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"Let\u2019s continue with this blog post series about SQL Server and Docker. A couple of days ago, I was in a customer shop that already implemented SQL Server 2017 on Linux as Docker containers. It was definitely a very interesting day with a lot of customer experience and feedbacks. We discussed with him about lot […]<\/p>\n","protected":false},"author":26,"featured_media":10830,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[601,1291,73,1292,51,1077],"type_dbi":[],"class_list":["post-10828","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","tag-docker","tag-docker0","tag-linux","tag-network-bridge","tag-sql-server","tag-sql-server-2017"],"acf":[],"yoast_head":"\n
SQL Server on Docker and network bridge considerations<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server on Docker and network bridge considerations\" \/>\n<meta property=\"og:description\" content=\"Let\u2019s continue with this blog post series about SQL Server and Docker. A couple of days ago, I was in a customer shop that already implemented SQL Server 2017 on Linux as Docker containers. It was definitely a very interesting day with a lot of customer experience and feedbacks. We discussed with him about lot […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-02-14T11:46:15+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-07-17T15:00:08+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"429\" \/>\n\t<meta property=\"og:image:height\" content=\"400\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Microsoft Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Microsoft Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/\"},\"author\":{\"name\":\"Microsoft Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"headline\":\"SQL Server on Docker and network bridge considerations\",\"datePublished\":\"2018-02-14T11:46:15+00:00\",\"dateModified\":\"2023-07-17T15:00:08+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/\"},\"wordCount\":1617,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg\",\"keywords\":[\"Docker\",\"Docker0\",\"Linux\",\"Network bridge\",\"SQL Server\",\"SQL Server 2017\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/\",\"name\":\"SQL Server on Docker and network bridge considerations\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg\",\"datePublished\":\"2018-02-14T11:46:15+00:00\",\"dateModified\":\"2023-07-17T15:00:08+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg\",\"width\":429,\"height\":400},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server on Docker and network bridge considerations\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\",\"name\":\"Microsoft Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"caption\":\"Microsoft Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/microsoft-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SQL Server on Docker and network bridge considerations","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/","og_locale":"en_US","og_type":"article","og_title":"SQL Server on Docker and network bridge considerations","og_description":"Let\u2019s continue with this blog post series about SQL Server and Docker. A couple of days ago, I was in a customer shop that already implemented SQL Server 2017 on Linux as Docker containers. It was definitely a very interesting day with a lot of customer experience and feedbacks. We discussed with him about lot […]","og_url":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/","og_site_name":"dbi Blog","article_published_time":"2018-02-14T11:46:15+00:00","article_modified_time":"2023-07-17T15:00:08+00:00","og_image":[{"width":429,"height":400,"url":"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg","type":"image\/jpeg"}],"author":"Microsoft Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Microsoft Team","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/"},"author":{"name":"Microsoft Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"headline":"SQL Server on Docker and network bridge considerations","datePublished":"2018-02-14T11:46:15+00:00","dateModified":"2023-07-17T15:00:08+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/"},"wordCount":1617,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg","keywords":["Docker","Docker0","Linux","Network bridge","SQL Server","SQL Server 2017"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/","url":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/","name":"SQL Server on Docker and network bridge considerations","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg","datePublished":"2018-02-14T11:46:15+00:00","dateModified":"2023-07-17T15:00:08+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg","width":429,"height":400},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-on-docker-and-network-bridge-considerations\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL Server on Docker and network bridge considerations"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4","name":"Microsoft Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","caption":"Microsoft Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/microsoft-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10828","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=10828"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10828\/revisions"}],"predecessor-version":[{"id":26786,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10828\/revisions\/26786"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/10830"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=10828"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=10828"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=10828"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=10828"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"blog](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-2.jpg\")
<\/td>\n![\"blog](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-1-docker-archi-1-e1518609873932.jpg\")
<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n![\"blog](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-3-docker-network-bridge-e1518610161517.jpg\")
<\/p>\n![\"blog](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-128-4-docker-network-bridge-sqlcmd.jpg\")
<\/p>\n