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

Open
#346 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
docker, docker-compose, rust
Domain
api, backend

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Rust
Stars
7.5k
Forks
329
Avg merge
7h 48m
Merged PRs (30d)
105

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libracoder/kiri

All issues in libracoder/kiri

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.