Compose file versioning in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Compose file version declaration

What is the purpose of specifying the version field at the top of a Docker Compose file?

A It defines the Docker Compose file format version, which determines available features and syntax.

B It sets the Docker Engine API version to use when running containers.

C It specifies the version of the base image used in all services.

D It controls the version of the Docker CLI installed on the host machine.

💡 Hint

Think about how Compose files evolve and how Docker knows which syntax rules to apply.

The version field in a Compose file tells Docker Compose which file format version to use. This affects which features and syntax are supported in the file.

💻 Command Output

intermediate

Output of docker-compose with unsupported version

Given this Compose file snippet, what will be the output or result when running docker-compose up?

version: '5.0'
services:
  web:
    image: nginx

Docker

version: '5.0'
services:
  web:
    image: nginx

A Starts the nginx container successfully with no warnings.

B SyntaxError: Invalid YAML format in Compose file.

C Error: Unsupported Compose file version "5.0". Supported versions are "3", "3.8", etc.

D Warning: Version 5.0 is deprecated, but containers start anyway.

💡 Hint

Check which Compose file versions are officially supported by Docker Compose.

Docker Compose does not support version 5.0. It will throw an error indicating the version is unsupported.

❓ Configuration

advanced

Compose file version and feature compatibility

Which Compose file version must be used to enable the profiles feature that allows conditional service startup?

A version: '2.4'

B version: '3.3'

C version: '3.7'

D version: '3.9'

💡 Hint

Profiles were introduced in a recent Compose file version starting with 3.x.

The profiles feature was introduced in Compose file version 3.9, allowing conditional service activation.

❓ Troubleshoot

advanced

Diagnosing version mismatch issues

You have a Compose file with version: '3.8' but when running docker-compose up, some features like secrets are not working as expected. What is the most likely cause?

A The Docker Engine version is too old and does not support Compose file 3.8 features.

B The Compose file syntax is incorrect and causes parsing errors.

C The <code>version</code> field must be removed to enable all features.

D Docker Compose does not support secrets in any version.

💡 Hint

Check compatibility between Docker Engine and Compose file features.

Some Compose file features require a minimum Docker Engine version. If the engine is outdated, features like secrets won't work even if the Compose file version is correct.

✅ Best Practice

expert

Choosing Compose file version for multi-environment projects

For a project that needs to run on both local developer machines and a cloud CI/CD pipeline with different Docker versions, which Compose file version strategy is best to ensure maximum compatibility?

A Use the latest Compose file version and require all environments to upgrade Docker.

B Use the lowest Compose file version supported by all environments, even if it limits features.

C Omit the <code>version</code> field entirely to let Docker Compose auto-detect features.

D Maintain multiple Compose files with different versions and merge them at runtime.

💡 Hint

Think about stability and compatibility across different environments.

Using the lowest common Compose file version ensures the file works everywhere, avoiding failures due to unsupported features or versions.

Practice

1. What does the version field in a Docker Compose file specify?

easy

A. The version of the operating system hosting Docker

B. The version of the Docker Engine installed on the system

C. The version of the application running inside the container

D. The format and features Docker Compose should use to read the file

Solution

1. Step 1: Understand the role of the version field

   The version field tells Docker Compose which syntax and features to expect in the file.

2. Step 2: Differentiate from other version types

   This field is not about Docker Engine, app, or OS versions but about Compose file format.

3. Final Answer:

   The format and features Docker Compose should use to read the file -> Option D

4. Quick Check:

   Compose file version = file format and features [OK]

Hint: Version field controls Compose syntax, not Docker or app versions [OK]

Common Mistakes:

• Confusing Compose file version with Docker Engine version
• Thinking it sets app container version
• Assuming it relates to OS version

2. Which of the following is the correct way to specify the Compose file version in YAML?

easy

A. version: "3.9"

B. version : 3.9

C. version = "3.9"

D. "version" : 3.9

Solution

1. Step 1: Recall YAML syntax for key-value pairs

   YAML uses colon and space to assign values, and strings should be quoted if they contain dots.

2. Step 2: Identify correct quoting for version

   The version number with a decimal should be quoted as a string: "3.9".

3. Final Answer:

   version: "3.9" -> Option A

4. Quick Check:

   YAML version field quoted with colon = correct [OK]

Hint: Use colon and quotes for version like version: "3.9" [OK]

Common Mistakes:

• Using equals sign instead of colon
• Not quoting version with decimals
• Putting quotes around key instead of value

3. Given this Compose file snippet:

version: "2.4"
services:
  web:
    image: nginx
    ports:
      - "80:80"

What will happen if you run this with Docker Compose version 1.27.0?

medium

A. It will run successfully using version 2 features

B. It will fail because version 2.4 is not supported in 1.27.0

C. It will ignore the version and run with default settings

D. It will upgrade the Compose file version automatically

Solution

1. Step 1: Check Docker Compose 1.27.0 compatibility

   Docker Compose 1.27.0 supports Compose file version 2.4 syntax and features.

2. Step 2: Understand behavior on supported versions

   Since version 2.4 is supported, Compose will run the services as defined without errors.

3. Final Answer:

   It will run successfully using version 2 features -> Option A

4. Quick Check:

   Supported Compose version runs fine [OK]

Hint: Check Compose version supports file version before running [OK]

Common Mistakes:

• Assuming newer Compose versions are always required
• Thinking Compose auto-upgrades file versions
• Believing unsupported versions cause silent ignores

4. You have this Compose file:

version: "3.8
services:
  app:
    image: myapp
    ports:
      - "8080:80"

When running docker-compose up, you get an error. What is the likely cause?

medium

A. The ports mapping syntax is incorrect

B. The image name is invalid without a tag

C. The version number is not quoted, causing a YAML parsing error

D. Docker Compose does not support version 3.8

Solution

1. Step 1: Identify YAML syntax issue

   The version field with a decimal must be quoted as a string to avoid YAML parsing errors.

2. Step 2: Check other fields for errors

   Image name without tag is valid (defaults to latest), ports syntax is correct, and version 3.8 is supported.

3. Final Answer:

   The version number is not quoted, causing a YAML parsing error -> Option C

4. Quick Check:

   Unquoted decimal version causes YAML error [OK]

Hint: Always quote version numbers with decimals in Compose files [OK]

Common Mistakes:

• Not quoting version with decimals
• Assuming image needs explicit tag
• Misreading ports syntax as error

5. You want to use a new Compose feature available only in version 3.9, but your current Compose file uses version "3.7". What is the best way to update your Compose file to use the new feature safely?

hard

A. Add the new feature without changing the version field, it will work automatically

B. Change the version field to "3.9" and test the file with your Docker Compose version

C. Downgrade your Docker Compose to an older version that supports 3.7 features only

D. Remove the version field entirely to let Docker Compose decide

Solution

1. Step 1: Update the version field to match the new feature

   Set the version field to "3.9" to indicate use of new features introduced in that version.

2. Step 2: Test compatibility with your Docker Compose version

   Ensure your Docker Compose installation supports version 3.9 to avoid errors.

3. Final Answer:

   Change the version field to "3.9" and test the file with your Docker Compose version -> Option B

4. Quick Check:

   Update version field and verify Compose support [OK]

Hint: Match version field to features and test Compose version support [OK]

Common Mistakes:

• Using new features without updating version field
• Removing version field causing unpredictable behavior
• Ignoring Compose version compatibility