Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#14,372 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
57/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
docker-compose, go
領域
backend, devops

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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

主要言語
Go
スター
38.5k
フォーク
5.9k
平均マージ
1日 17時間
マージ済み PR（30日）
63

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

docker/compose のほかの issue

docker/compose の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。