Secrets management in Docker - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to create a Docker secret named 'db_password' from a file.

Docker

docker secret [1] db_password ./password.txt

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

Ainspect

Blist

Crm

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'rm' instead of 'create' deletes secrets instead of creating them.

Using 'list' or 'inspect' only shows secrets but does not create them.

The docker secret create command is used to create a new secret in Docker Swarm.

2fill in blank

medium

Complete the Docker service command to use the secret 'db_password'.

Docker

docker service create --name mydb --secret [1] postgres

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

Amy_secret

Bdb_password

Cpassword

Dsecret_db

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different or incorrect secret name causes the service to fail to find the secret.

The secret name must match the one created earlier, which is 'db_password'.

3fill in blank

hard

Fix the error in the command to remove a Docker secret named 'db_password'.

Docker

docker secret [1] db_password

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

Adel

Bremove

Crm

Ddelete

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'delete' or 'del' which are not valid Docker secret commands.

The correct command to delete a Docker secret is docker secret rm.

4fill in blank

hard

Fill both blanks to create a Docker secret from a string.

Docker

echo '[1]' | docker secret create [2] -

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

Amysecretvalue

Bdb_password

Cuser_password

Dsecret_value

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up secret content and secret name.

Using different secret names inconsistently.

We echo the secret string 'mysecretvalue' and create a secret named 'db_password'.

5fill in blank

hard

Fill all three blanks to create a Docker service that uses two secrets and sets an environment variable.

Docker

docker service create --name app --secret [1] --secret [2] -e DB_PASS=[3] nginx

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

Adb_password

Bapi_key

Csecret_env

Ddb_password_value

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing secret names with environment variable values.

Using incorrect secret names.

The service uses secrets 'db_password' and 'api_key'. The environment variable DB_PASS is set to 'db_password_value'.

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