moby tested by Argusic Runner

What the test found

Built dockerd (Docker version dev, build c7b76b939) and docker-proxy and ran the unit suite (3237 tests, 27 container-capability-bound failures); api and client module suites passed with exit 0; the journald log-read suite passed with 48 subtests using an extracted systemd-journal-remote; no live daemon socket was started because unprivileged user namespaces are blocked and there is no root.

Real binary built and module tests pass, but a live daemon socket was impossible in this container: unprivileged user namespace creation returns EPERM (AppArmor/sysctl), no root to change it, and CAP_NET_ADMIN/CAP_SYS_ADMIN are absent. Journald tests were exercised against an extracted systemd-journal-remote (mock-style stand-in). All 27 unit failures reproduced as environment capability/absence-of-root constraints, not repo defects; latest upstream master still contains the same code paths.

Argusic installed moby in 20 minutes and launched it; verification reached Verified with mock services. 4 of 9 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of moby

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.