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

Abierto
#14,471 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker-compose, go
Área
cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Go
Estrellas
38.9k
Forks
6k
Merge medio
2 d 22 h
PR fusionados (30 d)
81

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de docker/compose

Todos los issues de docker/compose

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.