Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[BUG] A start failure in one service aborts the start of unrelated services (unreleased regression)

Aperta
  • Qualcosa non va?
#14,372 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
57/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker-compose, go
Ambito
backend, devops

Direzione di ricerca

Start by tracing the Compose start phase and the shared context cancellation described in the issue, then compare that flow with v5.6.0. Reproduce with the provided compose.yaml and commands; inspect why a failing web start aborts work for unrelated services such as api and db. Done means the command still reports the web failure while unrelated starts and pre_start work already in progress can finish.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

kind/bug
Description

On main, when one node in the start phase fails (port conflict, failing hook, unhealthy required dependency, --wait-timeout), the failure cancels the context shared by the whole start phase. Start, health wait and pre_start work still in flight for unrelated services is aborted too.

Current behavior (main, 20ca59586): a service whose configuration changed is recreated (old container removed) but never started. It is left in created state, so a service that was running before the command ends up stopped. No message is printed for it, and its Waiting progress line never completes. A pre_start hook container that is still running is killed.

Expected behavior (as in v5.6.0): the command still fails because of the failing service, but a start already in progress for an unrelated service runs to completion.

This does not happen with v5.6.0, so it looks like an unreleased regression.

Steps To Reproduce
  1. With this compose.yaml: 
    name: n1repro
services:
  db:
    image: alpine:3.20
    command: sleep infinity
    healthcheck: { test: ["CMD", "true"], interval: 2s }
  api:
    image: alpine:3.20
    command: sleep infinity
    environment: { VERSION: "${VERSION:-1}" }
    depends_on: { db: { condition: service_healthy } }
  web:
    image: nginx:alpine
    ports: ["18089:80"]
  2. Start everything: VERSION=1 docker compose up -d --wait
  3. Stop web and take its port: docker compose stop web && docker run -d --name blocker -p 18089:80 nginx:alpine
  4. Change api's configuration and run up again: VERSION=2 docker compose up -d (fails on web, as expected)
  5. Check api: docker inspect -f '{{.State.Status}}' n1repro-api-1
    • v5.6.0: running, recreated with VERSION=2 (2/2 runs)
    • main 20ca59586: created (2/2 runs). The output ends with Container n1repro-db-1 Waiting, and nothing follows for db or api.
Compose Version
Docker Compose version dev   # built from main at 20ca59586 (bad)
Docker Compose version dev   # built from v5.6.0 (good)
Docker Environment
Server Version: 29.1.3
Operating System: Docker Desktop
OSType: linux
Architecture: arch64
Kernel Version: 6.12.54-linuxkit
Storage Driver: overlayfs
Anything else?

No response

Lingua principale
Go
Stelle
38.4k
Fork
5.9k
Merge medio
1g 19h
PR unite (30g)
66

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di docker/compose

Tutte le issue di docker/compose

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.