docker compose up and down - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to start services defined in a Docker Compose file.

Docker

docker compose [1]

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

Aup

Bbuild

Cdown

Dps

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'down' instead of 'up' to start services.

Confusing 'build' with starting containers.

The docker compose up command starts all services defined in the Docker Compose file.

2fill in blank

medium

Complete the command to stop and remove containers, networks, and volumes created by Docker Compose.

Docker

docker compose [1]

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

Alogs

Bstart

Crestart

Ddown

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'start' or 'restart' instead of 'down'.

Confusing 'logs' with stopping containers.

The docker compose down command stops and removes containers, networks, and volumes created by docker compose up.

3fill in blank

hard

Fix the error in the command to start services in detached mode.

Docker

docker compose up [1]

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

A-d

B--detach

C-D

D--down

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase '-D' which is invalid.

Using '--down' which is not a valid flag.

The -d flag runs containers in detached mode (in the background).

4fill in blank

hard

Fill both blanks to specify a custom Compose file and start services.

Docker

docker compose -f [1] [2]

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

Acustom-compose.yml

Bup

Cdown

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'down' instead of 'up' to start services.

Not specifying the correct file name.

The -f option specifies the Compose file, and up starts the services.

5fill in blank

hard

Fill both blanks to stop services, remove containers, and remove volumes.

Docker

docker compose [1] --remove-orphans [2]

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

Adown

B--volumes

C--force

Dup

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'up' instead of 'down' to stop services.

Forgetting to add the '--volumes' flag to remove volumes.

docker compose down stops and removes containers. The --remove-orphans flag removes containers not defined in the Compose file. The --volumes flag removes volumes. The --force flag is not valid here but included as a distractor.

Practice

1. What does the command docker compose up do in a multi-container application?

easy

A. Deletes the docker-compose file

B. Stops and removes all containers

C. Starts all the containers defined in the docker-compose file

D. Builds images but does not start containers

Solution

1. Step 1: Understand the purpose of docker compose up

   This command reads the docker-compose.yml file and starts all the containers defined in it.

2. Step 2: Compare with other commands

   docker compose down stops and removes containers, so it is not the same as up.

3. Final Answer:

   Starts all the containers defined in the docker-compose file -> Option C

4. Quick Check:

   docker compose up = start containers [OK]

Hint: Remember: 'up' means start containers [OK]

Common Mistakes:

• Confusing 'up' with 'down'
• Thinking 'up' deletes files
• Assuming 'up' only builds images

2. Which of the following is the correct command to stop and remove all containers started by docker compose?

easy

A. docker compose stop

B. docker compose down

C. docker compose remove

D. docker compose kill

Solution

1. Step 1: Identify the command to stop and remove containers

   docker compose down stops and removes containers, networks, and default volumes created by up.

2. Step 2: Differentiate from other commands

   docker compose stop only stops containers but does not remove them. remove is not a valid command here.

3. Final Answer:

   docker compose down -> Option B

4. Quick Check:

   down = stop and remove [OK]

Hint: Use 'down' to stop and clean containers [OK]

Common Mistakes:

• Using 'stop' which doesn't remove containers
• Trying non-existent commands like 'remove'
• Confusing 'kill' with 'down'

3. Given this sequence of commands:
docker compose up -d
docker compose down
What will be the state of the containers after these commands?

medium

A. Containers are removed and not running

B. Containers are stopped but still exist

C. Containers are running in detached mode

D. Containers are paused

Solution

1. Step 1: Analyze docker compose up -d

   This starts containers in detached mode (running in background).

2. Step 2: Analyze docker compose down

   This stops and removes all containers started by up.

3. Final Answer:

   Containers are removed and not running -> Option A

4. Quick Check:

   up -d starts, down removes [OK]

Hint: 'down' removes containers even if started detached [OK]

Common Mistakes:

• Thinking containers remain stopped but not removed
• Confusing paused with stopped
• Assuming detached means containers stay after down

4. You ran docker compose down but your containers are still running. What is the most likely reason?

medium

A. You ran docker compose down in a different directory than the compose file

B. You forgot to add -d flag

C. The containers were started with docker run instead

D. Docker daemon is not running

Solution

1. Step 1: Understand how docker compose down works

   This command affects containers defined in the compose file in the current directory.

2. Step 2: Identify why containers remain running

   If run in a different directory, it won't find or stop those containers.

3. Final Answer:

   You ran docker compose down in a different directory than the compose file -> Option A

4. Quick Check:

   Correct directory needed for down [OK]

Hint: Run commands where your compose file is located [OK]

Common Mistakes:

• Thinking -d flag affects stopping containers
• Assuming down stops containers from docker run
• Not checking Docker daemon status

5. You want to restart your multi-container app with fresh containers, removing old volumes and networks. Which command should you run?

hard

A. docker compose up --build

B. docker compose stop && docker compose start

C. docker compose restart

D. docker compose down -v && docker compose up -d

Solution

1. Step 1: Understand the need to remove old volumes and networks

   Removing volumes requires the -v flag with docker compose down.

2. Step 2: Combine commands to remove and start fresh

   docker compose down -v removes containers, networks, and volumes; docker compose up -d starts fresh containers in detached mode.

3. Final Answer:

   docker compose down -v && docker compose up -d -> Option D

4. Quick Check:

   Use down -v to remove volumes before up [OK]

Hint: Use 'down -v' to remove volumes before 'up' [OK]

Common Mistakes:

• Using 'restart' which doesn't remove volumes
• Using 'stop' and 'start' which keep old volumes
• Assuming '--build' removes volumes