{"id":48457,"date":"2025-02-08T08:42:47","date_gmt":"2025-02-08T08:42:47","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=48457"},"modified":"2025-07-12T05:38:40","modified_gmt":"2025-07-12T05:38:40","slug":"docker-network","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/docker-network\/","title":{"rendered":"Docker commands Guide – docker network with examples"},"content":{"rendered":"\n

Here\u2019s a complete tutorial<\/strong> on docker network<\/code>, covering what it does<\/strong>, examples<\/strong>, and use cases<\/strong>.<\/p>\n\n\n\n

\n\n\n\n

What is docker network<\/code>?<\/strong><\/h2>\n\n\n\n

docker network<\/code> is a command used to manage Docker networks<\/strong>, enabling containers to communicate with each other<\/strong> and control how they connect internally and externally. Docker provides several types of networks (bridge, overlay, host, and macvlan), each suited for different use cases.<\/p>\n\n\n\n

Key Features:<\/strong><\/h3>\n\n\n\n
    \n
  • Create, inspect, connect, and disconnect networks<\/strong>.<\/li>\n\n\n\n
  • Control how containers communicate within and across multiple hosts.<\/li>\n\n\n\n
  • Supports custom and isolated networks<\/strong> for security and scalability.<\/li>\n<\/ul>\n\n\n\n
    \n\n\n\n

    Docker Network Types<\/strong><\/h2>\n\n\n\n

    1. Bridge Network (default)<\/strong><\/h3>\n\n\n\n
      \n
    • The most common type for standalone containers.<\/li>\n\n\n\n
    • Containers on the same bridge network can communicate with each other.<\/li>\n<\/ul>\n\n\n\n

      2. Host Network<\/strong><\/h3>\n\n\n\n
        \n
      • Removes network isolation; the container uses the host\u2019s network stack<\/strong> directly.<\/li>\n\n\n\n
      • Suitable for high-performance network communication.<\/li>\n<\/ul>\n\n\n\n

        3. Overlay Network<\/strong><\/h3>\n\n\n\n
          \n
        • Used for multi-host networking<\/strong> in Docker Swarm.<\/li>\n\n\n\n
        • Allows containers on different hosts to communicate securely.<\/li>\n<\/ul>\n\n\n\n

          4. Macvlan Network<\/strong><\/h3>\n\n\n\n
            \n
          • Assigns a MAC address<\/strong> to containers, making them appear as physical devices on the network.<\/li>\n\n\n\n
          • Useful for integrating Docker with existing physical networks.<\/li>\n<\/ul>\n\n\n\n
            \n\n\n\n

            Basic Syntax<\/strong><\/h2>\n\n\n
            docker<\/span> network<\/span> [COMMAND]<\/span> [OPTIONS]<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
            Common docker network<\/code> Commands:<\/h3>\n\n\n\n
              \n
            • create<\/code><\/strong>: Create a new network.<\/li>\n\n\n\n
            • ls<\/code><\/strong>: List all networks.<\/li>\n\n\n\n
            • inspect<\/code><\/strong>: Show detailed information about a network.<\/li>\n\n\n\n
            • connect<\/code><\/strong>: Connect a container to a network.<\/li>\n\n\n\n
            • disconnect<\/code><\/strong>: Disconnect a container from a network.<\/li>\n\n\n\n
            • rm<\/code><\/strong>: Remove a network.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n
              Examples of docker network<\/code> Commands<\/strong><\/h2>\n\n\n\n
              1. List All Docker Networks<\/strong><\/h3>\n\n\n
              docker network ls\n<\/code><\/span><\/pre>\n\n\n
              Example Output:<\/strong><\/p>\n\n\n
              NETWORK ID     NAME      DRIVER    SCOPE\n6e8<\/span>d77eabc12   bridge    bridge    local\n5<\/span>aeb2c1234ab   host      host      local\n9<\/span>a8d12345def   none      null<\/span>      local\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              2. Create a New Bridge Network<\/strong><\/h3>\n\n\n
              docker network create my_custom_network\n<\/code><\/span><\/pre>\n\n\n
              This creates a custom bridge network called my_custom_network<\/code>.<\/p>\n\n\n\n
              \n\n\n\n
              3. Create a Network with a Specific Subnet<\/strong><\/h3>\n\n\n
              docker network create \\\n  --subnet=192.168.1.0\/24 \\\n  custom_subnet_network\n<\/code><\/span><\/pre>\n\n\n
              This creates a network with the subnet 192.168.1.0\/24<\/code>.<\/p>\n\n\n\n
              \n\n\n\n
              4. Inspect a Network<\/strong><\/h3>\n\n\n
              docker network inspect my_custom_network\n<\/code><\/span><\/pre>\n\n\n
              This provides detailed information about the network, including connected containers and configuration.<\/p>\n\n\n\n
              \n\n\n\n
              5. Connect a Container to a Network<\/strong><\/h3>\n\n\n
              docker network connect my_custom_network my_container\n<\/code><\/span><\/pre>\n\n\n
              This connects my_container<\/code> to my_custom_network<\/code>.<\/p>\n\n\n\n
              \n\n\n\n
              6. Disconnect a Container from a Network<\/strong><\/h3>\n\n\n
              docker network disconnect my_custom_network my_container\n<\/code><\/span><\/pre>\n\n\n
              This disconnects my_container<\/code> from my_custom_network<\/code>.<\/p>\n\n\n\n
              \n\n\n\n
              7. Create an Overlay Network<\/strong><\/h3>\n\n\n
              docker network create \\\n  --driver overlay \\\n  my_overlay_network\n<\/code><\/span><\/pre>\n\n\n
              This creates an overlay network for multi-host communication (requires Docker Swarm).<\/p>\n\n\n\n
              \n\n\n\n
              8. Create a Macvlan Network<\/strong><\/h3>\n\n\n
              docker network create \\\n  -d macvlan \\\n  --subnet=192.168<\/span>.1<\/span>.0<\/span>\/24<\/span> \\\n  --gateway=192.168<\/span>.1<\/span>.1<\/span> \\\n  -o parent<\/span>=eth0 \\\n  my_macvlan_network\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
              This creates a macvlan network where containers get their own IP addresses in the 192.168.1.0\/24<\/code> subnet.<\/p>\n\n\n\n
              \n\n\n\n
              9. Remove a Network<\/strong><\/h3>\n\n\n
              docker network rm my_custom_network\n<\/code><\/span><\/pre>\n\n\n
              This removes the my_custom_network<\/code>.<\/p>\n\n\n\n
              \n\n\n\n
              10. Remove All Unused Networks<\/strong><\/h3>\n\n\n
              docker network prune\n<\/code><\/span><\/pre>\n\n\n
              This removes all unused networks.<\/p>\n\n\n\n
              \n\n\n\n
              11. Use a Custom Network When Running a Container<\/strong><\/h3>\n\n\n
              docker run --rm --network=my_custom_network nginx\n<\/code><\/span><\/pre>\n\n\n
              This runs an nginx<\/code> container attached to my_custom_network<\/code>.<\/p>\n\n\n\n
              \n\n\n\n
              12. List Connected Containers in a Network<\/strong><\/h3>\n\n\n
              docker network inspect my_custom_network | jq '.[0].Containers'<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              This lists all containers connected to my_custom_network<\/code> (requires jq<\/code> for JSON parsing).<\/p>\n\n\n\n
              \n\n\n\n
              Use Cases for docker network<\/code><\/strong><\/h2>\n\n\n\n
              1. Container Communication in Isolated Environments<\/strong><\/h3>\n\n\n\n
                \n
              • Use custom bridge networks to group related containers<\/strong> for secure communication.<\/li>\n\n\n\n
              • Example: Create a network for a web app and database<\/strong>, ensuring they can communicate internally.<\/li>\n<\/ul>\n\n\n\n
                \n\n\n\n
                2. High-Performance Networking with Host Mode<\/strong><\/h3>\n\n\n\n
                  \n
                • Use the host network<\/strong> for low-latency<\/strong> and high-performance applications like monitoring tools or network proxies.<\/li>\n\n\n\n
                • Example: Run a Prometheus<\/strong> container in host mode to reduce network overhead.<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n
                  3. Multi-Host Networking (Docker Swarm)<\/strong><\/h3>\n\n\n\n
                    \n
                  • Use overlay networks for distributed applications<\/strong> across multiple Docker hosts.<\/li>\n\n\n\n
                  • Example: Deploy a microservices application<\/strong> across a Docker Swarm cluster.<\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n
                    4. Integrating Docker with Physical Networks (Macvlan)<\/strong><\/h3>\n\n\n\n
                      \n
                    • Use macvlan networks to assign unique IP addresses<\/strong> to containers on your physical network.<\/li>\n\n\n\n
                    • Example: Deploy containers as part of your corporate network infrastructure.<\/li>\n<\/ul>\n\n\n\n
                      \n\n\n\n
                      5. Secure and Private Networks<\/strong><\/h3>\n\n\n\n
                        \n
                      • Create isolated networks for sensitive applications<\/strong> to prevent external access.<\/li>\n\n\n\n
                      • Example: Run an internal API service<\/strong> on a private network only accessible to specific containers.<\/li>\n<\/ul>\n\n\n\n
                        \n\n\n\n
                        6. Simplified CI\/CD Networking<\/strong><\/h3>\n\n\n\n
                          \n
                        • Create temporary networks in CI pipelines for testing container communication.<\/li>\n\n\n\n
                        • Example: Set up an isolated network<\/strong> for integration tests in a CI\/CD job.<\/li>\n<\/ul>\n\n\n\n
                          \n\n\n\n
                          List of Common docker network<\/code> Commands<\/strong><\/h2>\n\n\n\n
                          Command<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
                          docker network ls<\/code><\/td>List all networks<\/td><\/tr>
                          docker network create my_network<\/code><\/td>Create a new bridge network<\/td><\/tr>
                          docker network create --driver overlay my_overlay<\/code><\/td>Create an overlay network for multi-host setups<\/td><\/tr>
                          docker network inspect my_network<\/code><\/td>Inspect a network for detailed information<\/td><\/tr>
                          docker network connect my_network my_container<\/code><\/td>Connect a container to a network<\/td><\/tr>
                          docker network disconnect my_network my_container<\/code><\/td>Disconnect a container from a network<\/td><\/tr>
                          docker network rm my_network<\/code><\/td>Remove a network<\/td><\/tr>
                          docker network prune<\/code><\/td>Remove all unused networks<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                          \n\n\n\n
                          Best Practices for Using Docker Networks:<\/strong><\/h2>\n\n\n\n
                            \n
                          1. Use custom networks<\/strong> for container communication to avoid exposing services to the default bridge network.<\/li>\n\n\n\n
                          2. Isolate sensitive services<\/strong> on private networks for security.<\/li>\n\n\n\n
                          3. Monitor and prune unused networks<\/strong> to avoid network clutter.<\/li>\n\n\n\n
                          4. Use overlay networks<\/strong> for multi-host Docker Swarm deployments.<\/li>\n\n\n\n
                          5. Plan subnets<\/strong> carefully to avoid conflicts with your physical network.<\/li>\n<\/ol>\n\n\n\n
                            \n\n\n\n
                            Common Errors and Solutions<\/strong><\/h2>\n\n\n\n
                              \n
                            1. “Network not found”<\/strong>
                              \u2192 Ensure the network exists by checking with docker network ls<\/code>.<\/li>\n\n\n\n
                            2. “Address already in use”<\/strong>
                              \u2192 Choose a subnet that does not conflict with other networks on your host.<\/li>\n\n\n\n
                            3. “Cannot connect to container”<\/strong>
                              \u2192 Verify that the container is running and the network is properly configured.<\/li>\n\n\n\n
                            4. “Permission denied”<\/strong>
                              \u2192 Run the command with sudo<\/code> or check user permissions.<\/li>\n<\/ol>\n\n\n\n
                              \n\n\n\n
                              Combining docker network<\/code> with Other Commands<\/strong><\/h2>\n\n\n\n
                              Run a Web App with a Linked Database<\/strong><\/h3>\n\n\n
                              docker network create web_net\ndocker run -d --network=web_net --name=web_app my_web_app\ndocker run -d --network=web_net --name=db my_database\n<\/code><\/span><\/pre>\n\n\n
                              Inspect and Check for IP Conflicts<\/strong><\/h3>\n\n\n
                              docker network inspect my_network\n<\/code><\/span><\/pre>\n\n\n
                              Automate Network Cleanup<\/strong><\/h3>\n\n\n
                              docker network prune -f\n<\/code><\/span><\/pre>\n\n\n
                              \n\n\n\n
                              <\/p>\n","protected":false},"excerpt":{"rendered":"
                              Here\u2019s a complete tutorial on docker network, covering what it does, examples, and use cases. What is docker network? docker network is a command used to manage Docker networks, enabling… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[4862],"tags":[],"class_list":["post-48457","post","type-post","status-publish","format-standard","hentry","category-docker"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48457","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=48457"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48457\/revisions"}],"predecessor-version":[{"id":48459,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48457\/revisions\/48459"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=48457"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=48457"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=48457"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}