User namespace remapping in Docker - Mini Project: Build & Apply

User Namespace Remapping in Docker

📖 Scenario: You are setting up Docker on a Linux system where you want to improve security by isolating container users from host users. This is done by enabling user namespace remapping, which maps container user IDs to different host user IDs.This project will guide you step-by-step to configure Docker daemon to use user namespace remapping and verify it works.

🎯 Goal: Configure Docker daemon to enable user namespace remapping with a specific user and group, then run a container to verify the remapping is active.

📋 What You'll Learn

Create a Docker daemon configuration file with user namespace remapping enabled

Specify the remapping user and group in the configuration

Restart Docker daemon to apply the configuration

Run a Docker container and verify the user namespace remapping

💡 Why This Matters

🌍 Real World

User namespace remapping helps protect the host system by isolating container users, reducing risks if a container is compromised.

💼 Career

Understanding and configuring user namespace remapping is important for DevOps engineers and system administrators to enhance container security.

1

Create Docker daemon configuration file

Create a file called /etc/docker/daemon.json with the exact content: {"userns-remap": "default"} to enable user namespace remapping using the default user.

Docker

# Create /etc/docker/daemon.json with userns-remap set to "default"
# Your code here

Hint

Use echo and sudo tee to create the file with the exact JSON content.

2

Verify remapping user and group exist

Check that the system has a user called dockremap and a group called dockremap created for remapping by running id dockremap.

Docker

echo '{"userns-remap": "default"}' | sudo tee /etc/docker/daemon.json
# Run the command to check dockremap user and group
# Your code here

Hint

Use the id command to check if the dockremap user and group exist.

3

Restart Docker daemon to apply configuration

Restart the Docker service by running sudo systemctl restart docker to apply the user namespace remapping configuration.

Docker

echo '{"userns-remap": "default"}' | sudo tee /etc/docker/daemon.json
id dockremap
# Restart Docker daemon below
# Your code here

Hint

Use sudo systemctl restart docker to restart the Docker daemon.

4

Run a container and verify user namespace remapping

Run a Docker container with docker run --rm alpine id and observe the output. The uid and gid should be 0(root), confirming user namespace remapping is active and transparent to the container.

Docker

echo '{"userns-remap": "default"}' | sudo tee /etc/docker/daemon.json
id dockremap
sudo systemctl restart docker
# Run the container and print user info below
# Your code here

Hint

The output should show uid=0(root) and gid=0(root), indicating remapping is active.

Practice

1.

What is the main purpose of user namespace remapping in Docker?

easy

A. To allow containers to use more CPU cores

B. To increase container startup speed

C. To enable automatic container backups

D. To improve security by isolating container user IDs from host user IDs

Solution

1. Step 1: Understand user namespace remapping concept

   User namespace remapping changes container user IDs so they do not match host user IDs.

2. Step 2: Identify the security benefit

   This isolation reduces risk if a container is compromised, protecting the host system.

3. Final Answer:

   To improve security by isolating container user IDs from host user IDs -> Option D

4. Quick Check:

   User namespace remapping = security isolation [OK]

Hint: User namespace remapping isolates users for security [OK]

Common Mistakes:

• Thinking it improves performance
• Confusing with resource limits
• Assuming it enables backups

2.

Which of the following is the correct way to enable user namespace remapping in Docker's daemon.json file?

{
  "userns-remap": "default"
}

easy

A. { "userns-remap": true }

B. { "userns-remap": "enabled" }

C. { "userns-remap": "default" }

D. { "userns-remap": 1 }

Solution

1. Step 1: Check Docker daemon configuration syntax

   The correct key is "userns-remap" and it expects a string value like "default" or a username.

2. Step 2: Validate options

   Only { "userns-remap": "default" } uses the correct key and a valid string value "default".

3. Final Answer:

   { "userns-remap": "default" } -> Option C

4. Quick Check:

   Correct key and string value = { "userns-remap": "default" } [OK]

Hint: Use string "default" for userns-remap in daemon.json [OK]

Common Mistakes:

• Using boolean true instead of string
• Using numeric values
• Using invalid strings like "enabled"

3.

Given Docker daemon configured with "userns-remap": "default", what will be the output of id -u inside a container run as root?

medium

A. 100000

B. 0

C. 65534

D. 1

Solution

1. Step 1: Understand user ID remapping

   When user namespace remapping is enabled, the container runs in its own user namespace where root is UID 0 inside the container.

2. Step 2: Identify the output of id -u inside container

   Inside the container, id -u for the root user reports 0, as it views UIDs from the container's namespace perspective. The host sees the remapped UID (e.g., 100000).

3. Final Answer:

   0 -> Option B

4. Quick Check:

   id -u inside container shows 0 for root [OK]

Hint: Inside container, root UID is 0 despite host remapping [OK]

Common Mistakes:

• Confusing container-internal UID (0) with host-remapped UID (100000)
• Thinking remapping changes UID view inside container
• Choosing 65534 which is nobody user

4.

You enabled user namespace remapping in Docker but containers fail to start with permission errors. What is the most likely cause?

medium

A. The remapped user IDs do not have permission on container files

B. Docker daemon.json syntax is incorrect

C. Containers are using too much CPU

D. Docker version does not support user namespaces

Solution

1. Step 1: Analyze permission errors after enabling userns-remap

   User namespace remapping changes container user IDs, so files owned by root on host may not be accessible by remapped IDs.

2. Step 2: Identify cause of permission failure

   If the remapped user IDs lack permissions on container files or volumes, containers fail to start with permission denied errors.

3. Final Answer:

   The remapped user IDs do not have permission on container files -> Option A

4. Quick Check:

   Permission errors = remapped UID lacks file access [OK]

Hint: Check file permissions for remapped user IDs [OK]

Common Mistakes:

• Blaming daemon.json syntax without checking logs
• Assuming CPU limits cause permission errors
• Ignoring Docker version compatibility

5.

You want to run a container with user namespace remapping but need the container's root user to have access to a host directory /data. What is the best way to configure this?

hard

A. Change ownership of /data on host to the remapped UID range

B. Disable user namespace remapping for this container

C. Run the container as a non-root user

D. Mount /data as read-only volume

Solution

1. Step 1: Understand user namespace remapping effect on file access

   With remapping, container root maps to a high UID on host, so host files must be owned or accessible by that UID.

2. Step 2: Adjust host directory ownership

   Changing /data ownership to the remapped UID range allows container root to access it safely without disabling remapping.

3. Final Answer:

   Change ownership of /data on host to the remapped UID range -> Option A

4. Quick Check:

   Host directory ownership matches remapped UID for access [OK]

Hint: Match host directory ownership to remapped UID [OK]

Common Mistakes:

• Disabling remapping loses security benefits
• Running as non-root may not solve access needs
• Mounting read-only prevents write access