Skip to content

Installer: time limit on docker compose up (#376) - #378

Merged
rbardaji merged 2 commits into
mainfrom
feature/376-compose-timeout
Oct 23, 2026
Merged

rbardaji merged 2 commits into
mainfrom
feature/376-compose-timeout

Conversation

@rbardaji

Copy link
Copy Markdown
Collaborator

Closes #376.

What

  • docker compose up -d --build for the Endpoint and for the bundled CKAN now runs under timeout. The limit is set with --compose-timeout <n> (minutes, or seconds with an s suffix); the default is 30 minutes and 0 means no limit.
  • While it runs, a heartbeat line is printed every minute.
  • When the limit runs out, the installer stops with an actionable message: reach the registry with docker pull, check the Docker Hub rate limit and any proxy, then re-run. The message also mentions --compose-timeout.
  • A compose that fails outright now gives a message with its exit code. Before, the start step ended the run silently.
  • Without timeout (coreutils) there is no limit, and the installer warns about it.

Tests

  • New install/tests/test_compose_timeout.py: 10 tests, 6 of which fail on main.
  • Real test with Docker on a laptop:
    • with --compose-timeout 2s the real image build was stopped after 3s with the message;
    • re-running without the flag completed the install, healthy.

Release 0.34.60.

@rbardaji
rbardaji merged commit f0c7197 into main Oct 23, 2026
2 checks passed
@rbardaji
rbardaji deleted the feature/376-compose-timeout branch October 23, 2026 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Installer: compose up/build has no timeout — a stalled pull hangs the run indefinitely

1 participant