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

Ouverte Adaptée aux débutants
#14,522 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@ndeloof y travaille déjà.

Depuis le 17/11/2026.

  • #14526 par @ndeloof — ouverte

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
78/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
docker, docker-compose, go
Domaine
backend, cli

Piste de recherche

Commencez dans internal/inspect/port.go, à Ports, puis lisez internal/inspect/inspect_test.go et les tests existants de gestion des ports. Reproduisez le cas du port exposé mais non publié et vérifiez comment docker compose port gère les publishers avec PublishedPort == 0. Le travail est terminé lorsque le port demandé renvoie une erreur et que le mode liste l’omet, tandis que les ports publiés et le comportement de ps restent inchangés.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

"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.

Langage dominant
Go
Étoiles
38.9k
Forks
6k
Merge moyen
2 j 22 h
PR mergées (30 j)
81

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de docker/compose

Toutes les issues de docker/compose

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.