aiodocker

Python Docker API client based on asyncio and aiohttp

Runs with mockssource: GitHubPythonApache-2.0commit 178d8a0fc9fa

Python, Apache-2.0 licensed. The project labels itself: aiohttp, api client, asyncio, docker and python.

aiodocker runs, with stand-ins for the services it depends on. An Argusic agent installed it in 16 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

aiodocker 0.1.dev1 installed and tested: 80/80 unit tests pass (core library, context, SSH, events, system info) using a mock Docker API server; containers/images/exec/swarm tests require a real Docker daemon not available in this environment

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 86 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
86 / 100
cost of the verifying run
$0.08 (measured)
recorded runs
2
last tested
stars
539
forks
118
open issues
28
watchers
17
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . 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.

Time lost to each failure while testing aiodocker, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Docker daemon cannot start (no root permissions, no user namespaces for rootless mode)6 minutes
  • Tests that use Docker multiplexed streaming protocol (containers, images, execs, testcontainers) or docker subprocess (configs, secrets, swarm, nodes, services, dind) cannot run against mock2 minutes
  • uv not available (not in PATH)1 minute
  • docker CLI not installed in container1 minute
Install time
16 minutes
Cold machine to finish
21 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
cd /work/repo && .venv/bin/python -m pytest tests/test_flow_control_queue.py tests/test_jsonstream.py tests/test_stream.py tests/test_utils.py tests/test_docker_close.py tests/test_context.py tests/test_ssh.py tests/test_system.py tests/test_events.py --tb=no --no-header returned 80 passed in 0.49s
Model tokens used
505,766
Exact commit tested
178d8a0fc9fa
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

tests/test_system.py::test_system_info PASSED                            [ 96%]
tests/test_events.py::test_events_default_task PASSED                    [ 97%]
tests/test_events.py::test_events_provided_task PASSED                   [ 98%]
tests/test_events.py::test_events_no_task PASSED                         [100%]
================================ tests coverage ================================
_______________ coverage: platform linux, python 3.12.3-final-0 ________________
Coverage XML written to file coverage.xml
============================== 80 passed in 0.49s ==============================
All data collected. Here is the final report.
tokens used
505,766
All data collected. Here is the final report.

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

  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 16 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.

Of the 5 aiohttp projects Argusic has installed and timed, aiodocker was the 4th fastest to reach a running state, and 4 of 5 reached one at all.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.08
Argusic Runner1/3Unverified80.000.01

Topics (from GitHub)

aiohttpapi-clientasynciodockerpython

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/aiodocker.svg)](https://argusic.com/subject/aiodocker)

Questions

Does aiodocker run?
aiodocker runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 16 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test aiodocker?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 178d8a0fc9fa. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test aiodocker?
The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does aiodocker take to install?
16 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 aiodocker need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing aiodocker?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does aiodocker compare with the alternatives?
Of the 5 aiohttp projects Argusic has installed and timed, aiodocker was the 4th fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for aiodocker?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion