Docker compose in pipelines in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start Docker Compose services in a Jenkins pipeline.

Jenkins

sh 'docker-compose [1] -d'

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

Arestart

Bbuild

Cstop

Dup

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stop' instead of 'up' stops services instead of starting them.

Using 'build' only builds images but does not start containers.

The docker-compose up -d command starts the services in detached mode.

2fill in blank

medium

Complete the code to run Docker Compose with a specific file in a Jenkins pipeline.

Jenkins

sh 'docker-compose -f [1] up -d'

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

Adocker-compose.prod.yml

Bdocker-compose.yml

Cdocker-compose.override.yml

Ddocker-compose.dev.yml

Attempts:

3 left

💡 Hint

Common Mistakes

Using the default file name when a specific environment file is needed.

Choosing the override or dev file instead of the production file.

Using -f docker-compose.prod.yml runs Docker Compose with the production configuration file.

3fill in blank

hard

Fix the error in the Jenkins pipeline step to stop Docker Compose services.

Jenkins

sh 'docker-compose [1]'

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

Akill

Bdown

Cremove

Dstop

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stop' only stops containers but does not remove networks or volumes.

Using 'kill' forcefully stops containers but does not clean up.

The docker-compose down command stops and removes containers, networks, and volumes.

4fill in blank

hard

Fill both blanks to build and start Docker Compose services in one command.

Jenkins

sh 'docker-compose [1] && docker-compose [2] -d'

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

Abuild

Bup

Crestart

Dstop

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'restart' or 'stop' instead of 'build' or 'up'.

Running 'up' before 'build' which may use outdated images.

First, docker-compose build builds images, then docker-compose up -d starts the services in detached mode.

5fill in blank

hard

Fill all three blanks to run Docker Compose with a specific file, build images, and start services detached.

Jenkins

sh 'docker-compose -f [1] [2] && docker-compose -f [1] [3] -d'

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

Adocker-compose.yml

Bbuild

Cup

Dstop

Attempts:

3 left

💡 Hint

Common Mistakes

Using different files for build and up commands.

Using 'stop' instead of 'build' or 'up'.

This runs docker-compose -f docker-compose.yml build to build images, then docker-compose -f docker-compose.yml up -d to start services detached.

Practice

1. What is the main purpose of using docker-compose in Jenkins pipelines?

easy

A. To manage multiple containers together easily

B. To write Jenkins pipeline scripts

C. To build Java applications

D. To deploy Jenkins itself

Solution

1. Step 1: Understand Docker Compose role

   Docker Compose is designed to manage multiple containers as a group, making it easier to start, stop, and configure them together.

2. Step 2: Relate to Jenkins pipelines

   In Jenkins pipelines, Docker Compose helps run multiple related containers needed for testing or deployment in one step.

3. Final Answer:

   To manage multiple containers together easily -> Option A

4. Quick Check:

   Docker Compose = Manage multiple containers [OK]

Hint: Docker Compose groups containers for easy control [OK]

Common Mistakes:

• Confusing Docker Compose with Jenkins scripting
• Thinking it builds applications
• Assuming it deploys Jenkins itself

2. Which command correctly starts services defined in a docker-compose.yml file in detached mode within a Jenkins pipeline?

easy

A. docker-compose start -d

B. docker-compose up -d

C. docker-compose run -d

D. docker-compose exec -d

Solution

1. Step 1: Identify the command to start services

   The correct command to start all services in detached mode is docker-compose up -d. The -d flag runs containers in the background.

2. Step 2: Check other options

   docker-compose start starts existing containers but does not create new ones. docker-compose run runs a one-off container, not the whole set. docker-compose exec runs commands inside running containers, not start them.

3. Final Answer:

   docker-compose up -d -> Option B

4. Quick Check:

   Start services detached = up -d [OK]

Hint: Use 'up -d' to start all services in background [OK]

Common Mistakes:

• Using 'start -d' which is invalid
• Confusing 'run' with 'up'
• Using 'exec' to start containers

3. Given this Jenkins pipeline snippet, what will be the output of the sh step?

stage('Test') {
  steps {
    sh 'docker-compose up -d'
    sh 'docker-compose exec web curl -s http://localhost'
    sh 'docker-compose down'
  }
}

medium

A. Starts containers, runs curl inside 'web' container, then stops containers

B. Only starts containers, no curl command runs

C. Runs curl on host machine, then stops containers

D. Fails because 'docker-compose exec' cannot run in pipeline

Solution

1. Step 1: Analyze each command in the pipeline

   docker-compose up -d starts all services in background. docker-compose exec web curl -s http://localhost runs curl inside the 'web' container. docker-compose down stops and removes containers.

2. Step 2: Understand the sequence and output

   The commands run in order: start containers, execute curl inside 'web', then stop containers. This is the expected behavior in a pipeline.

3. Final Answer:

   Starts containers, runs curl inside 'web' container, then stops containers -> Option A

4. Quick Check:

   Up, exec inside container, down = Starts containers, runs curl inside 'web' container, then stops containers [OK]

Hint: Exec runs commands inside containers after 'up' [OK]

Common Mistakes:

• Thinking exec runs on host, not inside container
• Assuming curl won't run
• Believing exec can't run in pipeline

4. You wrote this Jenkins pipeline step:

sh 'docker-compose exec web curl http://localhost'

But it fails with "No such container: web" error. What is the most likely cause?

medium

A. The docker-compose.yml file is missing

B. The curl command is incorrect

C. docker-compose exec cannot run curl

D. The 'web' container is not running yet

Solution

1. Step 1: Understand the error message

   "No such container: web" means the container named 'web' is not running or does not exist at the time of the command.

2. Step 2: Identify the cause in pipeline context

   If the container is not started before the exec command, this error occurs. The curl command or docker-compose.yml presence is unrelated to this specific error.

3. Final Answer:

   The 'web' container is not running yet -> Option D

4. Quick Check:

   Exec needs running container = The 'web' container is not running yet [OK]

Hint: Start containers before exec commands [OK]

Common Mistakes:

• Blaming curl command syntax
• Assuming exec can't run curl
• Ignoring container start step

5. You want to run integration tests inside a Jenkins pipeline using Docker Compose. The tests run inside a container named app. Which pipeline snippet correctly starts services, runs tests inside app, and then cleans up?

hard

A. sh 'docker-compose exec app ./run-tests.sh'
sh 'docker-compose up -d'
sh 'docker-compose down'

B. sh 'docker-compose run app ./run-tests.sh'
sh 'docker-compose up -d'
sh 'docker-compose down'

C. sh 'docker-compose up -d'
sh 'docker-compose exec app ./run-tests.sh'
sh 'docker-compose down'

D. sh 'docker-compose down'
sh 'docker-compose up -d'
sh 'docker-compose exec app ./run-tests.sh'

Solution

1. Step 1: Start services before running tests

   Services must be started with docker-compose up -d before running commands inside containers.

2. Step 2: Run tests inside the 'app' container

   Use docker-compose exec app ./run-tests.sh to execute tests inside the running 'app' container.

3. Step 3: Clean up containers after tests

   Finally, stop and remove containers with docker-compose down to free resources.

4. Final Answer:

   sh 'docker-compose up -d' sh 'docker-compose exec app ./run-tests.sh' sh 'docker-compose down' -> Option C

5. Quick Check:

   Up, exec test, down = sh 'docker-compose up -d' sh 'docker-compose exec app ./run-tests.sh' sh 'docker-compose down' [OK]

Hint: Always start containers before exec, then clean up [OK]

Common Mistakes:

• Running exec before starting containers
• Using run instead of exec for tests
• Stopping containers before tests run