[FEATURE] Report all missing required environment variables in a single error

Aperta
#14,471 2 commenti 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
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker-compose, go
Ambito
cli

Direzione di ricerca

Start by tracing environment variable interpolation and required-variable validation in Docker Compose; the issue names no source files or tests. Check how docker compose config and docker compose up handle multiple missing variables, then identify the relevant tests. Done means both commands report all missing required variables together and start no containers when validation fails.

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

Descrizione

kind/feature status/0-triage
Description

When a Compose file contains multiple required environment variables, Docker Compose stops at the first missing variable during interpolation.
This means users must repeatedly run docker compose up, fix one variable, and run the command again to discover the next missing variable.
It would be helpful to collect all missing required variables and report them together before exiting.

Example

services:
  app:
    image: alpine:latest
    environment:
      DB_HOST: ${DB_HOST:?DB_HOST is required}
      DB_PASSWORD: ${DB_PASSWORD:?DB_PASSWORD is required}
      API_KEY: ${API_KEY:?API_KEY is required}

With all three variables unset, run:

docker compose up

Current behavior
Compose exits after reporting a single missing required variable. The remaining missing variables are discovered only on subsequent attempts.

Expected behavior
Compose validates all required variables and returns one consolidated error, for example:

Configuration validation failed:
  - DB_HOST: DB_HOST is required
  - DB_PASSWORD: DB_PASSWORD is required
  - API_KEY: API_KEY is required

No containers should be started when validation fails.
This behavior would be useful for both docker compose up and docker compose config.

Benefits

  • Reduces repeated configuration attempts.
  • Makes initial setup easier for projects with many required variables.
  • Provides clearer feedback in CI/CD logs.

Docker Compose version

PS C:\Users\<user>> docker compose version
Docker Compose version v5.3.1
PS C:\Users\<user>> docker version
Client:
 Version:           29.6.2-rd
 API version:       1.55
 Go version:        go1.26.4
 Git commit:        ede120b
 Built:             Fri Jul 17 17:00:40 2026
 OS/Arch:           windows/amd64
 Context:           default
Lingua principale
Go
Stelle
38.9k
Fork
6k
Merge medio
2g 22h
PR unite (30g)
81

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.