[BUG] `docker compose port` prints `:0` (exit 0) for a port the image exposes but the service does not publish

Abierto Apto para principiantes
#14,522 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@ndeloof ya está trabajando en esto.

Desde el 17/11/2026.

  • #14526 de @ndeloof — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker, docker-compose, go
Área
backend, cli

Línea de trabajo

Empieza en internal/inspect/port.go, en Ports; luego lee internal/inspect/inspect_test.go y las pruebas existentes de manejo de puertos. Reproduce el caso del puerto expuesto pero no publicado y comprueba cómo docker compose port maneja los publicadores con PublishedPort == 0. El trabajo estará terminado cuando el puerto solicitado dé un error y el modo de lista lo omita, mientras que los puertos publicados y el comportamiento de ps sigan igual.

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

Descripción

"This issue was filed by an AI agent on a human's behalf. The human submitter may not have independently verified the report."

Description

docker compose port SERVICE PRIVATE_PORT is documented to "print the public port for a specific mapping". When the private port is only exposed (e.g. an image EXPOSE) and has no host binding, it prints :0 and exits 0 instead of failing. In list mode (docker compose port SERVICE) the same port shows up as 6379/tcp -> :0.

docker port on the same container prints no public port '6379' published for ... with exit code 1, and lists nothing in list mode. #10039 (fixing #10010) already turned the "port not found → :0" case into an error; the exposed-but-unpublished case still goes through, because the container listing reports exposed ports with PublicPort: 0 and internal/inspect/port.go keeps them.

Real-world impact: a script doing ADDR=$(docker compose port db 6379) for a redis/postgres service that does not publish its port gets :0 and exit 0, and fails later with a confusing connection error.

Steps To Reproduce
services:
  web:
    image: nginx:alpine
    ports:
      - "8080:80"
  db:
    image: redis:alpine   # EXPOSE 6379, not published
$ docker compose -p portrepro up -d
$ docker compose -p portrepro port web 80     # control
0.0.0.0:8080                                  # rc=0
$ docker compose -p portrepro port db 6379
:0                                            # rc=0
$ docker compose -p portrepro port db
6379/tcp -> :0                                # rc=0

$ docker port portrepro-db-1 6379
no public port '6379' published for portrepro-db-1   # rc=1
$ docker port portrepro-db-1
                                              # (nothing), rc=0

Expected: port db 6379 fails like docker port does (with the existing "no port 6379/tcp for container ..." error), and list mode only lists published ports.

Compose Version
main @ ed25575984c8 (built locally: go build -o bin/docker-compose ./cmd)
Docker Environment
Server Version: 29.5.2 (colima VM, Ubuntu 24.04 aarch64), client on macOS arm64
Anything else?

Suggested fix: skip publishers with PublishedPort == 0 in internal/inspect/port.go (Ports). containerPublishers is shared with ps, which should keep showing 6379/tcp like docker ps, so it is left unchanged. With that change: port db 6379 → no port 6379/tcp for container portrepro-db-1: 6379/tcp, rc=1; port db → empty; port web 80 / port web unchanged. A unit test in internal/inspect/inspect_test.go (TestPortsSkipsExposedButUnpublishedPorts) fails on main and passes with the change. Happy to open the PR once this is triaged.

AI disclosure: Claude Code (Anthropic) found the issue, ran the reproduction, and drafted this report, the patch and the test.

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.