ezarr
Ezarr aims to make it as easy as possible to setup an entire Servarr/Jackett/BitTorrent/Usenet/PleX/Jellyfin mediacenter stack using Docker
Runs with mockssource: GitHubPythonMITcommit cc6a12a182d1
Python, MIT licensed. The project labels itself: docker, docker compose, jackett, jellyfin, lidarr, mylar3, overseerr and plex.
ezarr runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1 minute and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Python CLI generates correct docker-compose.yml for all 18 supported services, all modules compile without errors, timezone auto-detection works, and edge cases (no services, empty inputs) are handled gracefully.
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 92 of 100 (the mean of this project's run scores).
At a glance
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.
- Install time
- 1 minutes
- Cold machine to finish
- under a minute
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- python3 -c 'all container_configs services generate valid output with image: lines'; simulated CLI through all services confirmed docker-compose.yml generation; python3 -m py_compile on all 3 modules passed; 'no services' path exits code 1 with error message
- Model tokens used
- 36,966
- Exact commit tested
- cc6a12a182d1
- 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.
- Tested edge cases: all "no" services exits cleanly, timezone detection parses `/etc/localtime` co… - `ContainerConfig` produces valid docker-compose YAML for every supported service (18 total) - `Homarr` encryption key generation produces 64-char hex strings from `os.urandom(32)` ## Verification The product here is a docker-compose generation CLI, not an app with a server. I proved the code wo… 1. Running the full CLI interactively (all services selected) — it generated a correct docker-compo… 2. Running individual module tests asserting correct output for all 18 services 3. Running the "no services" path — exits gracefully with code 1 4. Verifying timezone auto-detection works from `/etc/localtime` 5. Confirming all Python files compile cleanly The only thing I couldn't test is the `setup.sh` script (requires sudo) and `docker compose up` (re… ## Final JSON
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
- Installed in 1 minute, faster than the median of the 23 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, 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.
Of the 24 docker projects Argusic has installed and timed, ezarr was the 4th fastest to reach a running state, and 17 of 24 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.03 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.05 |
Topics (from GitHub)
dockerdocker-composejackettjellyfinlidarrmylar3overseerrplexplex-media-serverprowlarrqbittorrentradarrreadarrsabnzbdservarrsonarrtautullitorrentusenet
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ezarr)Questions
- Does ezarr run?
- ezarr runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test ezarr?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cc6a12a182d1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ezarr?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ezarr take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does ezarr need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ezarr?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does ezarr compare with the alternatives?
- Of the 24 docker projects Argusic has installed and timed, ezarr was the 4th fastest to reach a running state, and 17 of 24 reached one at all.
- Where is the evidence for ezarr?
- 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.