Docker compose in pipelines in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Docker Compose Up in Jenkins Pipeline

What will be the output of the following Jenkins pipeline snippet when it runs the Docker Compose up command?

Jenkins

pipeline {
  agent any
  stages {
    stage('Start Services') {
      steps {
        script {
          sh 'docker-compose up -d'
        }
      }
    }
  }
}

A Starts all services defined in docker-compose.yml in detached mode and prints container IDs

B Fails with error: 'docker-compose' command not found

C Starts services but runs in foreground blocking the pipeline

D Prints the docker-compose.yml content without starting services

💡 Hint

Think about what the '-d' flag does in docker-compose up command.

The '-d' flag runs containers in detached mode, so the command starts services and prints container IDs without blocking the pipeline.

❓ Configuration

intermediate

Correct Jenkinsfile Syntax for Docker Compose

Which Jenkinsfile snippet correctly runs 'docker-compose down' to stop and remove containers in a pipeline stage?

A stage('Stop Services') { steps { sh 'docker-compose stop' } }

B stage('Stop Services') { steps { sh docker-compose down } }

C stage('Stop Services') { steps { sh "docker-compose down" } }

D stage('Stop Services') { steps { sh 'docker-compose down' } }

💡 Hint

Check the correct way to pass shell commands as strings in Jenkins pipeline.

The command must be passed as a quoted string to the sh step. Option D uses single quotes correctly.

❓ Troubleshoot

advanced

Troubleshooting Docker Compose Service Not Starting

In a Jenkins pipeline, the 'docker-compose up' command runs but the service fails to start. Which is the most likely cause?

A The docker-compose.yml file is missing the 'version' field

B The Jenkins agent does not have Docker installed or running

C The pipeline script uses 'sh' instead of 'bat' on Linux

D The Jenkinsfile is missing the 'agent any' declaration

💡 Hint

Think about what is required for docker-compose commands to work on the Jenkins agent.

Docker and Docker Compose must be installed and the Docker daemon running on the Jenkins agent to start services.

🔀 Workflow

advanced

Best Practice for Using Docker Compose in Jenkins Pipeline

Which workflow step is best to ensure Docker Compose services are cleaned up after tests in a Jenkins pipeline?

A Run 'docker-compose rm -f' before 'docker-compose up'

B Run 'docker-compose stop' before starting services

C Run 'docker-compose down' in a post-build cleanup stage

D Run 'docker-compose restart' after tests finish

💡 Hint

Consider how to properly remove containers and networks after pipeline completion.

'docker-compose down' stops and removes containers, networks, and volumes, cleaning up resources after tests.

🧠 Conceptual

expert

Understanding Docker Compose Exit Codes in Jenkins

If a service in 'docker-compose up' fails to start, what exit code does the command return, and how should Jenkins handle it?

A Non-zero exit code; Jenkins should fail the pipeline immediately

B Zero exit code; Jenkins continues regardless of service status

C Non-zero exit code; Jenkins ignores it by default and continues

D Zero exit code; Jenkins retries the command automatically

💡 Hint

Think about how shell commands signal failure and Jenkins pipeline behavior.

Docker Compose returns a non-zero exit code if any service fails to start, causing Jenkins to fail the pipeline unless handled.

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