FG
💻 Software☁️ Cloud & DevOpsDocker

[BUG] `'version' is obsolete`

Fresh3 days ago
Mar 14, 20260 views
Confidence Score69%
69%

Problem

Description After updating to version v2.25.0, the command `docker compose pull docker-compose.yaml` gives the error `'version' is obsolete` Steps To Reproduce _No response_ Compose Version [code block] Docker Environment [code block] Anything else? _No response_

Error Output

error `'version' is obsolete`

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Unverified Fix
New Fix – Awaiting Verification

Update Docker Compose File Version

Medium Risk

The error message `'version' is obsolete` indicates that the version specified in the docker-compose.yaml file is no longer supported in the updated Docker Compose version v2.25.0. This typically occurs when the version specified is outdated or incompatible with the current Docker Compose functionality.

Awaiting Verification

Be the first to verify this fix

  1. 1

    Check Current Docker Compose Version

    Verify the currently installed version of Docker Compose to ensure compatibility.

    bash
    docker compose version
  2. 2

    Update docker-compose.yaml Version

    Edit the docker-compose.yaml file to use a supported version. Replace the existing version with '3.8' or '3.9', which are commonly supported versions.

    yaml
    version: '3.8'
  3. 3

    Validate docker-compose.yaml Syntax

    Run the following command to validate the syntax of the updated docker-compose.yaml file.

    bash
    docker compose config
  4. 4

    Pull Docker Images

    After updating the version and validating the syntax, attempt to pull the Docker images again using the updated docker-compose.yaml file.

    bash
    docker compose pull
  5. 5

    Test Application Deployment

    Deploy the application to ensure that all services defined in the docker-compose.yaml file are functioning correctly.

    bash
    docker compose up -d

Validation

Confirm that the command 'docker compose pull' runs without errors and that the application services start correctly with 'docker compose up -d'.

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

dockerdocker-composecontainerskind/bugstatus/0-triage