Ambassador container pattern in Docker - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the Docker command to run an ambassador container named 'amb' that forwards traffic to port 8080.

Docker

docker run -d --name amb -p 9090:[1] ambassador-image

Drag options to blanks, or click blank then click option'

A8080

B3000

C443

D80

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong port number for forwarding.

Confusing host and container ports.

The ambassador container forwards traffic from port 9090 on the host to port 8080 inside the container.

2fill in blank

medium

Complete the Docker Compose service definition to link the ambassador container to the main app container.

Docker

services:
  app:
    image: myapp
  ambassador:
    image: ambassador-image
    depends_on:
      - [1]

Drag options to blanks, or click blank then click option'

Aproxy

Bdatabase

Ccache

Dapp

Attempts:

3 left

💡 Hint

Common Mistakes

Linking to unrelated services like database or cache.

Missing the depends_on field.

The ambassador container depends on the main app container to forward traffic correctly.

3fill in blank

hard

Fix the error in the ambassador container's environment variable to set the target host correctly.

Docker

environment:
  TARGET_HOST=[1]

Drag options to blanks, or click blank then click option'

A"app"

Bapp

C"localhost"

Dlocalhost

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting string values.

Using localhost instead of the service name.

Environment variables with string values must be quoted in Docker Compose YAML.

4fill in blank

hard

Fill both blanks to complete the ambassador container's command to forward traffic to the app service on port 8080.

Docker

command: ["[1]", "[2]"]

Drag options to blanks, or click blank then click option'

Aproxy

Bapp

C8080

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' instead of 'proxy'.

Wrong port number.

The ambassador runs the 'proxy' command forwarding to port 8080.

5fill in blank

hard

Fill all three blanks to define a Docker Compose network and attach both app and ambassador containers to it.

Docker

networks:
  [1]:
    driver: [2]

services:
  app:
    image: myapp
    networks:
      - [3]
  ambassador:
    image: ambassador-image
    networks:
      - [3]

Drag options to blanks, or click blank then click option'

Afrontend_net

Bbridge

Dhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using different network names in definition and services.

Using 'host' driver which is less common.

The network is named 'frontend_net' using the 'bridge' driver, and both services join it.

Practice

1. What is the main role of an ambassador container in the ambassador container pattern?

easy

A. It acts as a helper proxy inside the same pod as your application.

B. It stores application data persistently.

C. It builds Docker images automatically.

D. It manages user authentication directly.

Solution

1. Step 1: Understand the ambassador container role

   The ambassador container acts as a proxy that helps your app communicate with external services.

2. Step 2: Differentiate from other container roles

   Unlike storage or build containers, the ambassador focuses on networking inside the pod.

3. Final Answer:

   It acts as a helper proxy inside the same pod as your application. -> Option A

4. Quick Check:

   Ambassador container = helper proxy [OK]

Hint: Ambassador = proxy helper inside pod [OK]

Common Mistakes:

• Confusing ambassador with storage or build containers
• Thinking ambassador manages authentication directly
• Assuming ambassador runs outside the pod

2. Which of the following is the correct way to link an application container to an ambassador container in a Kubernetes pod YAML?

easy

A. Use separate pods for app and ambassador with no shared network.

B. Use a Docker volume to share files between app and ambassador containers.

C. Define both containers under the same pod spec with shared localhost communication.

D. Expose the ambassador container on a public IP address.

Solution

1. Step 1: Understand pod container communication

   Containers in the same pod share the network namespace and can communicate over localhost.

2. Step 2: Identify correct linking method

   Defining both containers in the same pod spec allows the app to talk to ambassador via localhost.

3. Final Answer:

   Define both containers under the same pod spec with shared localhost communication. -> Option C

4. Quick Check:

   Same pod = localhost communication [OK]

Hint: Same pod containers communicate via localhost [OK]

Common Mistakes:

• Thinking ambassador must be in a separate pod
• Using volumes for network communication
• Exposing ambassador publicly instead of internal proxy

3. Given this pod spec snippet, what will be the hostname your app container uses to reach the ambassador container?

{
  "containers": [
    {"name": "app", "image": "myapp"},
    {"name": "ambassador", "image": "ambassador-image"}
  ]
}

medium

A. "external-service"

B. "ambassador"

C. "127.0.0.1"

D. "localhost"

Solution

1. Step 1: Understand pod networking

   Containers in the same pod share the network namespace, so they communicate over localhost or 127.0.0.1.

2. Step 2: Identify hostname for ambassador

   The ambassador container listens on localhost inside the pod, so the app uses "localhost" or "127.0.0.1" to reach it.

3. Final Answer:

   "localhost" -> Option D

4. Quick Check:

   Same pod communication = localhost [OK]

Hint: Same pod containers use localhost to communicate [OK]

Common Mistakes:

• Using container name as hostname inside pod
• Using external service name instead of localhost
• Confusing IP addresses inside pod

4. You have an ambassador container configured, but your app cannot reach the external service through it. What is a likely cause?

medium

A. The ambassador container is not running in the same pod as the app container.

B. The app container is using localhost to reach the ambassador.

C. The ambassador container is exposing port 8080 internally.

D. The external service is reachable directly by the app.

Solution

1. Step 1: Check pod configuration

   If ambassador is not in the same pod, app cannot reach it via localhost.

2. Step 2: Understand communication failure

   Without shared network namespace, localhost won't connect to ambassador, causing failure.

3. Final Answer:

   The ambassador container is not running in the same pod as the app container. -> Option A

4. Quick Check:

   Ambassador outside pod = no localhost access [OK]

Hint: Ambassador must be in same pod for localhost access [OK]

Common Mistakes:

• Assuming localhost works across pods
• Ignoring ambassador container status
• Confusing internal port exposure with connectivity

5. You want to improve security by restricting your app's access to an external database using the ambassador container pattern. Which approach best achieves this?

hard

A. Allow the app container to connect directly to the database and use ambassador only for logging.

B. Configure the ambassador container to handle all database connections and apply network policies to block direct app access.

C. Run the ambassador container in a separate pod with public IP to filter traffic.

D. Disable the ambassador container and let the app connect directly for simplicity.

Solution

1. Step 1: Use ambassador as controlled proxy

   Configure ambassador to manage all database connections, acting as a gatekeeper.

2. Step 2: Apply network policies

   Block direct app access to the database, forcing traffic through ambassador for security.

3. Final Answer:

   Configure the ambassador container to handle all database connections and apply network policies to block direct app access. -> Option B

4. Quick Check:

   Ambassador proxy + network policies = secure access [OK]

Hint: Use ambassador as proxy and block direct app access [OK]

Common Mistakes:

• Allowing direct app access to database
• Running ambassador outside pod with public IP
• Disabling ambassador for simplicity