Container DNS and service discovery in Docker - Time & Space Complexity

Time Complexity: Container DNS and service discovery

O(n)

Understanding Time Complexity

When containers communicate, they often use DNS to find each other by name. Understanding how the time to resolve these names grows helps us see how well service discovery scales.

We want to know: How does the time to find a container by name change as the number of containers grows?

Scenario Under Consideration

Analyze the time complexity of the following Docker Compose service discovery setup.

version: '3'
services:
  web:
    image: nginx
    depends_on:
      - api
    networks:
      - appnet
  api:
    image: myapi
    networks:
      - appnet
networks:
  appnet:
    driver: bridge

This setup lets the web service find the api service by its DNS name within the appnet network.

Identify Repeating Operations

Look at what happens when a container tries to resolve another container's name:

• Primary operation: DNS lookup queries sent to the embedded DNS server.
• How many times: Once per service name resolution, but the DNS server may check its list of container names.

The dominant work is the DNS server searching its list of known containers to match the requested name.

How Execution Grows With Input

As the number of containers (n) in the network grows, the DNS server must search through more names.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The number of checks grows directly with the number of containers. More containers mean more work to find a name.

Final Time Complexity

Time Complexity: O(n)

This means the time to resolve a container name grows linearly as the number of containers increases.

Common Mistake

[X] Wrong: "DNS lookups always take the same time no matter how many containers exist."

[OK] Correct: The DNS server must search through its list of container names, so more containers mean more work and longer lookup times.

Interview Connect

Understanding how service discovery scales helps you design systems that stay fast as they grow. This skill shows you can think about real-world system behavior, not just code.

Self-Check

"What if the DNS server used a hash map instead of a list to store container names? How would the time complexity change?"

Practice

1. What does Docker's built-in DNS service provide for containers on the same user-defined network?

easy

A. It assigns static IP addresses to containers.

B. It allows containers to find each other by their container names.

C. It disables network communication between containers.

D. It automatically updates container images.

Solution

1. Step 1: Understand Docker user-defined networks

   User-defined networks enable containers to communicate using DNS names instead of IP addresses.

2. Step 2: Role of Docker DNS service

   Docker's DNS service resolves container names to their current IP addresses on the same network.

3. Final Answer:

   It allows containers to find each other by their container names. -> Option B

4. Quick Check:

   Docker DNS = container name resolution [OK]

Hint: Containers use names, not IPs, to find each other on user networks [OK]

Common Mistakes:

• Thinking Docker assigns static IPs by default
• Believing DNS disables container communication
• Confusing DNS with image updates

2. Which Docker command correctly creates a user-defined network named my-net to enable container DNS service discovery?

easy

A. docker network create my-net

B. docker create network my-net

C. docker network new my-net

D. docker network build my-net

Solution

1. Step 1: Identify correct Docker network creation syntax

   The correct command to create a network is docker network create <name>.

2. Step 2: Verify options

   The options using 'docker network new', 'docker create network', and 'docker network build' have incorrect syntax; only docker network create my-net matches Docker syntax.

3. Final Answer:

   docker network create my-net -> Option A

4. Quick Check:

   Correct command = docker network create [OK]

Hint: Use 'docker network create' to make user-defined networks [OK]

Common Mistakes:

• Using 'docker create network' instead of 'docker network create'
• Confusing 'new' or 'build' with network creation
• Omitting the network name

3. Given two containers web and db on the same user-defined network, what will be the output of docker exec web ping -c 1 db if db is running?

medium

A. Ping succeeds showing db IP address and response time.

B. Ping fails with 'unknown host db' error.

C. Ping succeeds but shows IP of web container.

D. Ping command is not available inside containers.

Solution

1. Step 1: Understand container DNS on user-defined networks

   Containers on the same user-defined network can resolve each other's names to IP addresses.

2. Step 2: Effect of ping command

   Running ping from web to db will resolve db to its IP and send ICMP packets successfully if db is running.

3. Final Answer:

   Ping succeeds showing db IP address and response time. -> Option A

4. Quick Check:

   Container DNS + ping = success if target running [OK]

Hint: Ping container name on same network to test DNS and connectivity [OK]

Common Mistakes:

• Assuming ping fails due to IP changes
• Confusing container names with hostnames outside network
• Believing ping is unavailable inside containers

4. You created two containers on a user-defined network, but web cannot resolve db by name. What is the most likely cause?

medium

A. The web container has no network interface.

B. The db container is stopped.

C. Docker daemon is not running.

D. Containers are on different Docker networks.

Solution

1. Step 1: Check network configuration

   Containers must be on the same user-defined network for DNS name resolution to work.

2. Step 2: Analyze failure cause

   If web cannot resolve db, they are likely on different networks, so DNS does not link them.

3. Final Answer:

   Containers are on different Docker networks. -> Option D

4. Quick Check:

   Different networks block DNS resolution [OK]

Hint: Ensure containers share the same user-defined network for DNS [OK]

Common Mistakes:

• Assuming stopped container causes DNS failure (it causes ping failure)
• Thinking Docker daemon status affects container DNS directly
• Believing container can lack network interface if running

5. You want to deploy a multi-container app with a web server and database. You want the web server to always connect to the database by name, even if the database container restarts and gets a new IP. Which Docker setup ensures this?

hard

A. Run containers on separate networks and link them with --link option.

B. Use the default bridge network and hardcode the database container's IP address in the web server config.

C. Create a user-defined network and run both containers attached to it; use the database container's name in the web server config.

D. Assign static IPs manually to both containers on the default network.

Solution

1. Step 1: Understand service discovery with user-defined networks

   User-defined networks provide automatic DNS resolution by container name, even if IPs change.

2. Step 2: Evaluate options for reliable name-based connection

   Create a user-defined network and run both containers attached to it; use the database container's name in the web server config. uses user-defined network and container names, which is the recommended way for service discovery.

3. Step 3: Why other options fail

   Default bridge network lacks automatic DNS; hardcoding IPs breaks if IP changes; --link is deprecated; static IPs are complex and error-prone.

4. Final Answer:

   Create a user-defined network and run both containers attached to it; use the database container's name in the web server config. -> Option C

5. Quick Check:

   User-defined network + container names = reliable service discovery [OK]

Hint: Use user-defined network and container names for stable service discovery [OK]

Common Mistakes:

• Hardcoding IP addresses instead of using container names
• Using default bridge network without DNS support
• Relying on deprecated --link option
• Manually assigning static IPs unnecessarily