HOW TO CREATE A SIMPLE DOCKER NETWORK?—?with job scenario/ticket

A step by step guide create a docker network

Introduction: In the fast-paced world of DevOps, where containerization is king, Docker networks play a pivotal role in managing and isolating applications. To illustrate the process, let’s dive into a real-world scenario where the Nautilus DevOps team is tasked with creating Docker networks for various applications.

Scenario: “You’re a member of the Nautilus DevOps team, and your team has just received a critical ticket. The task at hand is to create Docker networks for different applications on “App Server 2” located in the “Stratos DC” data center. The specific requirements for this ticket are as follows:

a. Create a Docker network named “beta” on App Server 2 in Stratos DC.

b. Configure it to use macvlan drivers.

c. Set it to use subnet 10.10.1.0/24 and iprange 10.10.1.2/24.”

Let’s walk through this task step by step, ensuring that you can tackle similar challenges in your DevOps journey.

Step 1: Securely Access App Server 2

To begin, establish a secure SSH connection to “App Server 2” in the “Stratos DC.” Replace <username> and <app-server-2-ip> with the appropriate values:

ssh [email protected]        

Step 2: Create the “beta” Docker Network

Use the following command to create the “beta” Docker network, ensuring it adheres to the specified configurations:

docker network create -d macvlan - subnet=10.10.1.0/24 - ip-range=10.10.1.2/24 beta        

Here’s what each part of the command does:

- -d macvlan: Specifies the use of the macvlan driver, which allows containers to have their MAC addresses. - ?—?subnet=10.10.1.0/24: Sets the subnet for the network to 10.10.1.0/24. - ?—?ip-range=10.10.1.2/24: Defines the IP range within the subnet for container assignment. - beta: The name of the Docker network.

Step 3: Verify the Docker Network Creation

To ensure the “beta” network was created successfully, list all Docker networks:

docker network ls        

You should see “beta” in the list of networks, confirming that it has been created and is ready for use.

Step 4: Leverage the “beta” Network

With the “beta” network in place, you can now utilize it for your applications. Containers connected to this network will be able to communicate with each other using their assigned IP addresses within the specified range.

docker run --network=beta -d --name=webapp-container webapp-image
docker run --network=beta -d --name=db-container db-image        

Here, we’ve launched two containers, “container1” and “container2,” connected to the “beta” network. They can seamlessly communicate over this isolated network.

Conclusion:

Configuring Docker networks, as demonstrated in this scenario, is a fundamental skill for any DevOps professional. By following these steps, you can create Docker networks with specific configurations to isolate your applications effectively. This ability is invaluable when managing complex containerized environments, ensuring that your applications run securely and efficiently.

Reference:

Kodekloud

#devops #docker #network #devopsengineer #secops #devsecops #gabrielokom #kubernetes