Network isolation between services in Docker - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is network isolation between services in Docker?

Network isolation means keeping Docker containers separated so they cannot communicate unless explicitly allowed. This helps improve security and control over service interactions.

beginner

How do Docker networks help with service isolation?

Docker networks create separate virtual networks. Containers on different networks cannot talk to each other unless connected to a common network, enabling isolation.

beginner

What command creates a new isolated Docker network?

Use docker network create my_isolated_network to create a new isolated network.

beginner

How to run a container attached to a specific Docker network?

Use docker run --network my_isolated_network my_image to attach a container to the isolated network.

intermediate

Why is network isolation important in microservices?

It limits communication to only necessary services, reducing security risks and accidental data leaks between services.

Which Docker command creates a new isolated network?

A docker network new my_network

B docker create network my_network

C docker network create my_network

D docker network build my_network

The correct command is docker network create my_network to create a new network.

If two containers are on different Docker networks, can they communicate by default?

A Yes, always

B No, not unless connected to a common network

C Only if they share the same image

D Only if they run on the same host

Containers on different Docker networks cannot communicate unless connected to a shared network.

What flag attaches a container to a specific Docker network when running it?

A --net

B --link

C --connect

D --network

The correct flag is --network to specify the network for the container.

Why use network isolation between microservices?

A To limit communication and improve security

B To reduce image size

C To enable automatic updates

D To improve container startup speed

Network isolation limits communication between services, improving security.

Which Docker network type provides isolation by default?

A none

B host

C bridge

D overlay

The none network disables all networking, providing full isolation.

Explain how Docker networks can be used to isolate services and why this is useful.

Think about how separating rooms in a house can keep conversations private.

Describe the steps to create an isolated Docker network and run a container on it.

Imagine creating a private chat group and inviting only certain friends.

Practice

1. What is the main purpose of network isolation between Docker services?

easy

A. To keep services separate and control their communication

B. To speed up container startup time

C. To reduce the size of Docker images

D. To automatically update containers

Solution

1. Step 1: Understand network isolation concept

   Network isolation means keeping services separate so they don't communicate unless allowed.

2. Step 2: Identify the main goal

   The main goal is to control communication and improve security between services.

3. Final Answer:

   To keep services separate and control their communication -> Option A

4. Quick Check:

   Network isolation = separate and control communication [OK]

Hint: Network isolation means controlling service communication [OK]

Common Mistakes:

• Confusing network isolation with image size optimization
• Thinking it speeds up container startup
• Assuming it updates containers automatically

2. Which Docker command creates a custom network for isolating services?

easy

A. docker image build my-network

B. docker container run my-network

C. docker network create my-network

D. docker service start my-network

Solution

1. Step 1: Identify command to create network

   The command to create a Docker network is docker network create followed by the network name.

2. Step 2: Match correct syntax

   docker network create my-network uses the correct syntax: docker network create my-network.

3. Final Answer:

   docker network create my-network -> Option C

4. Quick Check:

   Creating network = docker network create [OK]

Hint: Use 'docker network create' to make custom networks [OK]

Common Mistakes:

• Using 'docker container run' to create networks
• Confusing image build with network creation
• Trying to start a service to create a network

3. Given two containers attached to different custom networks, what happens if one tries to ping the other by container name?

medium

A. Ping succeeds because Docker allows cross-network communication by default

B. Ping fails because containers on different networks cannot resolve each other's names

C. Ping succeeds only if both containers share the same image

D. Ping fails unless both containers are on the default bridge network

Solution

1. Step 1: Understand Docker network isolation

   Containers on different custom networks cannot communicate or resolve each other's names by default.

2. Step 2: Analyze ping behavior

   Since they are on separate networks, ping by container name will fail due to no DNS resolution across networks.

3. Final Answer:

   Ping fails because containers on different networks cannot resolve each other's names -> Option B

4. Quick Check:

   Different networks = no name resolution [OK]

Hint: Containers on different networks can't ping by name [OK]

Common Mistakes:

• Assuming default bridge allows all communication
• Thinking image similarity affects network reachability
• Believing Docker allows cross-network DNS by default

4. You created two services on the same custom network but they cannot communicate. What is the most likely mistake?

medium

A. The services have the same container name

B. The network was created with the wrong driver

C. The services are not attached to the same network

D. The containers are running on different Docker hosts

Solution

1. Step 1: Check network attachment

   If services are on the same network, they should communicate unless other factors block it.

2. Step 2: Consider Docker host location

   If containers run on different Docker hosts without overlay network, they cannot communicate even on the same network name.

3. Final Answer:

   The containers are running on different Docker hosts -> Option D

4. Quick Check:

   Different hosts without overlay = no communication [OK]

Hint: Check if containers run on same host or overlay network [OK]

Common Mistakes:

• Assuming same network name means same network across hosts
• Ignoring network driver type
• Confusing container names with network connectivity

5. You want two services to communicate but keep them isolated from all other containers. Which is the best approach?

hard

A. Create a custom network and attach only these two services to it

B. Use the default bridge network for both services

C. Attach both services to multiple networks including default

D. Run both services on the host network

Solution

1. Step 1: Understand isolation needs

   To isolate two services from others, they must be on a private network only they share.

2. Step 2: Choose network setup

   Creating a custom network and attaching only these two services ensures isolation and communication.

3. Step 3: Evaluate other options

   Default bridge includes all containers, multiple networks reduce isolation, host network removes isolation.

4. Final Answer:

   Create a custom network and attach only these two services to it -> Option A

5. Quick Check:

   Custom network with only two services = isolation + communication [OK]

Hint: Use custom network with only needed services attached [OK]

Common Mistakes:

• Using default network which includes all containers
• Attaching services to multiple networks losing isolation
• Using host network which disables isolation