[BUG] Negative replica count in scale flags (docker compose scale / --scale) is accepted without validation

Ouverte
#14,482 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@arsalanyavari y travaille déjà.

Depuis le 10/11/2026.

  • #14483 par @arsalanyavari — ouverte

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
30/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
À l'abandon
Stack technique
docker-compose, go
Domaine
backend, cli

Piste de recherche

The report identifies the scale and up --scale CLI paths but names no source files or tests. Start by tracing how each command parses and validates replica counts, then find the corresponding tests. Done means both commands reject negative counts while accepting zero and positive counts; an open linked pull request is already addressing this issue.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

kind/bug status/approved
Description

According to the Compose Specification, scale must be a non-negative integer (>= 0). The Compose file loader already enforces this and rejects negative scale: values in compose.yaml.

Additionally, the CLI properly validates non-numeric inputs — for instance, docker compose scale web=abc immediately returns:

invalid scale specifier: can't parse replica value as int: web=abc

However, when passing a negative replica count through the CLI flags, such as docker compose scale web=-1 or docker compose up --scale web=-1, the value is accepted without any validation error. The service is then assigned a negative replica count, which leads to unexpected behavior during convergence and container lifecycle handling.

The CLI should validate that the replica count is non-negative, consistent with the Compose Specification and with how the compose file loader treats negative scales.

Steps To Reproduce
  1. Create a minimal compose.yaml:
    services:
      web:
        image: alpine
    
  2. Attempt to scale the service with a negative replica count:
    docker compose scale web=-1
    
    Or:
    docker compose up --dry-run --scale web=-1
    
Observed Result
  • docker compose scale web=-1:

    [+] scale 1/1
     ✔ Network a_default Created                                                                                    0.0s
    service "web" has no container to start
    

    The negative value -1 is accepted without any validation error.

  • docker compose up --dry-run --scale web=-1:

    end of 'compose up' output, interactive run is not supported in dry-run mode
    

    The command finishes without warning or error regarding the negative replica count.

Compose Version
$ docker compose version
Docker Compose version v5.5.0
Docker Environment
Docker version 29.9.3, build 5457199aa5
Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.17.2
    Path:     /path/to/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v5.5.0
    Path:     /path/to/.docker/cli-plugins/docker-compose
Anything else?

No response

Langage dominant
Go
Étoiles
38.9k
Forks
6k
Merge moyen
2 j 22 h
PR mergées (30 j)
81

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de docker/compose

Toutes les issues de docker/compose

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.