Docker-Traefik
Docker media and home server stack with Docker Compose, Traefik, CrowdSec, Google OAuth2/Authelia, and LetsEncrypt. Built with Deployrr and UDMS guides/videos.
Could not verifysource: GitHubhomepageShellMITcommit 5ab37c2f11b7
Shell, MIT licensed. The project labels itself: bash script, docker, docker compose, jellyfin, plex, portainer, radarr and rclone.
Argusic could not get Docker-Traefik running. An Argusic agent installed it in 12 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 4 Docker Compose stacks validate successfully (83 services total), 9 broken YAML middleware files fixed, 1 network name mismatch corrected, Docker CLI/compose tools installed, but Docker daemon cannot start in this containerized 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 50 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Docker daemon unavailable - no root access and user namespace creation disabled8 minutes
- 9 YAML files had invalid Go template syntax inside double-quoted strings (e.g. customFrameOptionsValue: "allow-from https:{{env "DOMAIN.."}}") which broke YAML parsing2 minutes
- docker-compose-ds918.yml defined t2_proxy network but included services referenced traefik_proxy1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- docker compose config on all 4 compose files returned valid configs: hs=31 services, mds=9 services, ds918=13 services, ws-arm=30 services
- Model tokens used
- 401,169
- Exact commit tested
- 5ab37c2f11b7
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
# Let me check process start time ps -o lstart= -p $$ 2>/dev/null' in /work/repo succeeded in 0ms: Git initial commit: Wed Oct 15 22:02:57 UTC 2025 Current time: Fri Sep 25 04:32:12 UTC 2026 Diff seconds: 29744955 Diff minutes: 495749 Fri Sep 25 04:32:11 2026 All compose files validated, configs fixed. Here's the final result: tokens used 401,169 All compose files validated, configs fixed. Here's the final result:
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 12 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
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 | 3/3 | Did not run | 50.00 | 0.09 | |
| Argusic Runner | 2/3 | Did not run | 50.00 | 0.09 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.16 |
Topics (from GitHub)
bash-scriptdockerdocker-composejellyfinplexportainerradarrrclonesonarrsynologytraefiktransmissionwordpress
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/docker-traefik)Questions
- Does Docker-Traefik run?
- Argusic could not verify that Docker-Traefik runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test Docker-Traefik?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5ab37c2f11b7. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Docker-Traefik?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Docker-Traefik take to install?
- 12 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 Docker-Traefik need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Docker-Traefik?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Docker-Traefik?
- All 3 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.