`/info` returns an empty `SystemTime`, which breaks attached `docker compose up` and `docker compose logs -f` on Compose 5.7+

Aperta
#346 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
65/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker, docker-compose, rust
Ambito
api, backend

Direzione di ricerca

Start at the implementation of the Docker /info endpoint and trace how it builds the response; the issue does not name a source file or test. Find how the daemon's guest clock is available and how /info fields are tested. Done means SystemTime is returned as an RFC 3339 timestamp from that clock, and attached docker compose up and docker compose logs -f no longer fail with the reported error.

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

Descrizione

bug
Kiri version and system

0.2.1 (macOS), Docker CLI 29.9.3, engine API 1.47 (kiri reports server 27.5.1), Docker Compose v5.7.1

What you did

With the kiri Docker context selected, in a Compose project:

$ docker info --format '{{json .SystemTime}}'
$ docker compose up
$ docker compose logs -f
What happened

SystemTime is empty:

$ docker info --format '{{json .SystemTime}}'
""

docker compose up creates and starts the containers, then exits as soon as it tries to attach:

$ docker compose up

...
Attaching to api, db, elasticmq
reading the daemon time to subscribe to container events: the daemon reports no system time

docker compose logs -f fails with the same error.

What you expected instead

With Docker Engine (and Docker Desktop or Colima), /info returns SystemTime as an RFC 3339 timestamp with nanoseconds, taken from the daemon's clock:

"SystemTime": "2026-11-16T05:22:26.123456789Z"

With that, docker compose up attaches and streams logs, and docker compose logs -f follows them. The value should come from the guest/daemon clock, the one container events are stamped with, not the Mac's.

Anything else

It happens every time.

Compose only started reading this field in v5.7.0, in docker/compose@4ede2fa49f ("fix(monitor): subscribe to events since before the initial listing"). Attached up and logs -f now use SystemTime as the since point for the events subscription, and an empty value is a hard error (internal/logstream/monitor.go):

if res.Info.SystemTime == "" {
    return errors.New("reading the daemon time to subscribe to container events: the daemon reports no system time")
}

Earlier Compose versions don't read SystemTime, which is probably why this hasn't come up before.

Workaround: docker compose up -d, then docker logs -f <container>. Neither subscribes to events, and both work on kiri.

Lingua principale
Rust
Stelle
7.5k
Fork
329
Merge medio
7h 48m
PR unite (30g)
105

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 libracoder/kiri

Tutte le issue di libracoder/kiri

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.