Skip to content

ci: Check that the Moby daemon starts with extensions - #13

Open
vvoland wants to merge 1 commit into
moby:mainfrom
vvoland:work-ci
Open

vvoland wants to merge 1 commit into
moby:mainfrom
vvoland:work-ci

Conversation

@vvoland

@vvoland vvoland commented Oct 23, 2026

Copy link
Copy Markdown
Collaborator

The moby-integration job only ran the extension integration tests, which manage their own daemons.
A dockerd that failed to start with its default settings could go unnoticed.

The moby-integration job only ran the extension integration tests,
which manage their own daemons.
A dockerd that failed to start with its default settings could go
unnoticed.

Signed-off-by: Paweł Gronowski <git@grono.dev>
@vvoland vvoland self-assigned this Oct 23, 2026
@vvoland
vvoland requested a balanced review from Copilot October 23, 2026 13:05

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The focused CI change checks daemon startup with failure reporting and cleanup, and no blocking issues were identified.

No open issues 🎉

What changed in this PR

Adds a daemon startup smoke check to the Moby integration job, covering startup failures that extension integration tests could miss because they manage their own daemons.

Changes:

  • Builds and starts the Moby daemon inside the development container.
  • Polls for readiness and checks docker version and docker info.
  • Cleans up the daemon and prints its logs on failure.
File Description
.github/​workflows/​ci.yml Adds the daemon startup check before extension integration tests.

Review effort: Balanced

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.

2 participants