Secrets management in Docker - Step-by-Step Execution

Process Flow - Secrets management

Create Secret

↓

Store Secret Securely

↓

Deploy Service with Secret

↓

Container Accesses Secret

↓

Secret Used in Container

↓

Secret Removed After Use

This flow shows how a secret is created, stored securely, deployed to a container, accessed inside, and then removed after use.

Execution Sample

Docker

docker secret create my_secret ./secret.txt

docker service create --name my_service --secret my_secret nginx

docker exec <container_id> cat /run/secrets/my_secret

This code creates a secret, deploys a service using it, and shows how to access the secret inside the container.

Process Table

Step	Action	Command/Operation	Result/Output
1	Create secret from file	docker secret create my_secret ./secret.txt	Secret 'my_secret' created with ID abc123
2	Deploy service with secret	docker service create --name my_service --secret my_secret nginx	Service 'my_service' created and running
3	Find container ID	docker ps --filter name=my_service	Container ID: def456
4	Access secret inside container	docker exec def456 cat /run/secrets/my_secret	Contents of secret.txt displayed
5	Remove service	docker service rm my_service	Service 'my_service' removed
6	Remove secret	docker secret rm my_secret	Secret 'my_secret' removed

💡 Secrets are removed after service deletion to keep them secure.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 5	After Step 6
Secret 'my_secret'	Not created	Created and stored securely	Attached to service 'my_service'	Service removed, secret still exists	Secret removed from Docker

Key Moments - 3 Insights

Why can't I see the secret file on my host after creating it?

The secret is stored inside Docker's encrypted storage and only mounted inside containers at /run/secrets. It is not visible on the host filesystem directly (see execution_table step 4).

What happens to the secret when I remove the service?

Removing the service detaches the secret from running containers but does not delete the secret itself. You must remove the secret explicitly (see execution_table steps 5 and 6).

Can multiple services use the same secret?

Yes, you can attach the same secret to multiple services securely without duplicating it (implied by secret management design).

Visual Quiz - 3 Questions

Look at the execution table, at which step is the secret first accessible inside the container?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Access secret inside container' action in the execution_table at step 4.

According to the variable tracker, what is the state of the secret after step 5?

A Secret is still stored but service is removed

B Secret is attached to running service

C Secret is removed from Docker

D Secret is not created yet

💡 Hint

Look at the 'Secret 'my_secret'' row in variable_tracker after step 5.

If you forget to remove the secret after deleting the service, what happens?

A Secret is automatically deleted

B Secret remains stored in Docker

C Secret is lost and cannot be recovered

D Service restarts automatically

💡 Hint

Refer to execution_table steps 5 and 6 about secret removal.

Concept Snapshot

Docker Secrets Management:
- Create secret: docker secret create <name> <file>
- Deploy service with secret: docker service create --secret <name>
- Secrets mounted at /run/secrets/<name> inside containers
- Secrets are encrypted and not visible on host
- Remove secrets explicitly after service removal
- Multiple services can share secrets securely

Full Transcript

Secrets management in Docker involves creating secrets from files, storing them securely encrypted, and attaching them to services. When a service runs, the secret is mounted inside the container at /run/secrets/<secret_name>. The secret is not visible on the host filesystem. After the service is removed, the secret remains stored until explicitly deleted. This ensures secrets are managed securely and only accessible to authorized containers.

Practice

1. What is the main purpose of using docker secrets in a Docker environment?

easy

A. To securely store sensitive data like passwords outside of Docker images

B. To speed up container startup time

C. To increase the size of Docker images

D. To manage container networking settings

Solution

1. Step 1: Understand what secrets are

   Secrets are sensitive data such as passwords or keys that should not be stored inside images or code.

2. Step 2: Identify the purpose of Docker secrets

   Docker secrets provide a secure way to store and manage this sensitive data outside of images, making it available only to authorized services.

3. Final Answer:

   To securely store sensitive data like passwords outside of Docker images -> Option A

4. Quick Check:

   Secrets = Secure sensitive data storage [OK]

Hint: Secrets keep passwords safe outside images [OK]

Common Mistakes:

• Thinking secrets speed up containers
• Confusing secrets with networking
• Assuming secrets increase image size

2. Which of the following commands correctly creates a Docker secret named db_password from a file password.txt?

easy

A. docker secret create db_password password.txt

B. docker secret add db_password password.txt

C. docker secret new db_password password.txt

D. docker secret generate db_password password.txt

Solution

1. Step 1: Recall Docker secret creation syntax

   The correct command to create a secret is docker secret create [name] [file].

2. Step 2: Match the command with options

   docker secret create db_password password.txt matches the correct syntax exactly.

3. Final Answer:

   docker secret create db_password password.txt -> Option A

4. Quick Check:

   docker secret create = correct syntax [OK]

Hint: Use 'docker secret create' to add secrets from files [OK]

Common Mistakes:

• Using 'add' instead of 'create'
• Using 'new' or 'generate' which are invalid
• Confusing secret commands with service commands

3. Given the following Docker service creation command:

docker service create --name myapp --secret db_password nginx

What happens to the secret db_password inside the running container?

medium

A. It is stored as an environment variable named DB_PASSWORD

B. It is printed in the container logs

C. It is mounted as a file in /run/secrets/db_password

D. It is embedded inside the container image

Solution

1. Step 1: Understand how Docker secrets are exposed

   Docker secrets are mounted as files inside the container at /run/secrets/[secret_name].

2. Step 2: Analyze the options

   It is mounted as a file in /run/secrets/db_password correctly states the secret is mounted as a file. Options A, B, and D are incorrect because secrets are not environment variables, not printed in logs, and not embedded in images.

3. Final Answer:

   It is mounted as a file in /run/secrets/db_password -> Option C

4. Quick Check:

   Secrets = files in /run/secrets [OK]

Hint: Secrets appear as files in /run/secrets inside containers [OK]

Common Mistakes:

• Thinking secrets become environment variables automatically
• Expecting secrets to be logged
• Assuming secrets are inside the image

4. You run docker secret create mysecret secret.txt but get an error: Error: secret file secret.txt not found. What is the most likely cause?

medium

A. The secret already exists

B. The file secret.txt does not exist in the current directory

C. Docker daemon is not running

D. You used the wrong secret name

Solution

1. Step 1: Understand the error message

   The error says the file secret.txt was not found, meaning Docker cannot locate the file to create the secret.

2. Step 2: Identify the cause

   This usually means the file is missing or the path is incorrect. The file secret.txt does not exist in the current directory matches this cause. Other options do not relate to file not found errors.

3. Final Answer:

   The file secret.txt does not exist in the current directory -> Option B

4. Quick Check:

   File missing = secret create error [OK]

Hint: Check file path exists before creating secret [OK]

Common Mistakes:

• Assuming secret name causes file error
• Ignoring Docker daemon status
• Thinking secret existence causes file not found

5. You want to update a secret api_key used by a running Docker service webapp. Which sequence of commands correctly updates the secret without downtime?

hard

A. Edit the secret file inside the running container

B. Directly overwrite the existing secret with docker secret update

C. Stop the service, delete the secret, create new secret with same name, then start service

D. Create new secret with a different name, update service to use new secret, then remove old secret

Solution

1. Step 1: Understand Docker secret immutability

   Docker secrets cannot be updated directly; they are immutable once created.

2. Step 2: Update secret safely

   The recommended way is to create a new secret with a new name, update the service to use this new secret, then remove the old secret to avoid downtime.

3. Step 3: Analyze options

   Create new secret with a different name, update service to use new secret, then remove old secret follows this process. Directly overwrite the existing secret with docker secret update is invalid because docker secret update does not exist. Stop the service, delete the secret, create new secret with same name, then start service causes downtime. Edit the secret file inside the running container is impossible because secrets are mounted read-only.

4. Final Answer:

   Create new secret with a different name, update service to use new secret, then remove old secret -> Option D

5. Quick Check:

   Secrets immutable = create new and update service [OK]

Hint: Create new secret and update service to avoid downtime [OK]

Common Mistakes:

• Trying to overwrite existing secret
• Stopping service causing downtime
• Editing secrets inside container