moby
The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
Runssource: GitHubGoApache-2.0commit c7b76b939576
Go, Apache-2.0 licensed. The project labels itself: containers, docker, go and golang.
moby runs. An Argusic agent installed it in 75 minutes and hit 8 errors on a clean machine with no GPU, and the whole session was recorded.
Go 1.26.8 toolchain installed from tarball. docker-proxy binary builds and prints help. ~150 unit test package suites pass; 8 failures due to missing container capabilities (no root, no libsystemd headers, no SCTP, no Windows platform). API and client module unit tests all pass.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 80 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- cmd/docker-proxy: 4 SCTP tests fail - protocol not supported in this container
- daemon/config: config merge/validation tests fail due to environment config differences
- daemon/graphdriver/vfs: tests require mount capability not available in unprivileged container
- daemon/graphdriver/windows: Windows-only platform tests incompatible with Linux
- daemon/volume/safepath: tests require mount capability not available in unprivileged container
- daemon/libnetwork/netutils: tests require netns capability not available in unprivileged container
- Install time
- 75 minutes
- Cold machine to finish
- 76 minutes
- Errors hit and fixed
- 8 hit, 0 fixed with no human help
- How the result was proved
- go test -mod=readonly -tags netgo -test.timeout=2m on each package with tests; docker-proxy built with go build and ./docker-proxy --help returned usage text (exit 0); API module go test ./... all pass; Client module go test ./... all pass
- Model tokens used
- 354,071
- Exact commit tested
- c7b76b939576
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
The project is now fully set up and verified. Here's the summary: **What was done:** - **Go 1.26.8** downloaded from go.dev and installed (no Go was available initially) - All module dependencies cached via `go mod download` - **docker-proxy binary** built and verified — `/tmp/docker-proxy --help` prints usage text (exit 0) - **Unit tests** run comprehensively across all three Go modules **Test results:** - **API module** (6 packages) — all pass - **Client module** (22 packages) — all pass - **Root module** (~140+ packages) — ~96% pass rate - 8 pre-existing failures, all environment-constrained: no root/sudo (no mount, netns, iptables), n… The ARGUSIC_RESULT line above contains the complete JSON report as required.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 75 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Hit 8 errors during setup, 8 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/moby)Questions
- Does moby run?
- Yes. moby runs. Argusic installed and launched it on a clean machine in 75 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test moby?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c7b76b939576. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test moby?
- The run that produced this verdict cost $0.39: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does moby take to install?
- 75 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does moby need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing moby?
- 8 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
- Where is the evidence for moby?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.