All-jellyfin-media-server
Self-hosted complete media server Jellyfin with sonarr, radarr, jackett, prowlarr, qbittorrent, flaredolverr and gluetun Nord VPN Proton VPN in docker compose
Could not verifysource: GitHubhomepageShellMITcommit d0e84b8f7950
Shell, MIT licensed. The project labels itself: docker, docker compose, film, gluetun, install, jackett, jellyfin and jellyseerr.
Argusic could not get All-jellyfin-media-server running. An Argusic agent installed it in 30 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All project YAML compose files and shell scripts are syntactically valid, but the container lacks a Docker daemon and the mount syscall is blocked, making it impossible to launch any Docker Compose services.
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 20 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.
- No Docker daemon available in this unprivileged container15 minutes
- containerd v2.4.2 starts but cannot mount overlayfs layers (mount syscall blocked)8 minutes
- Cannot install system packages via apt (not root)2 minutes
- no Docker socket found anywhere on filesystem2 minutes
- Install time
- 30 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- docker-compose-plugin validated compose config; containerd starts and serves GRPC but cannot mount overlay layers (operation not permitted); no Docker socket accessible on any path
- Model tokens used
- 427,502
- Exact commit tested
- d0e84b8f7950
- 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.
4. Static Docker CLI (v29.9.1) can run client commands 5. containerd (v2.4.2) starts but cannot mount layers 6. Python podman-compose (v1.6.0) is installed in venv === What doesn't work === 1. No Docker daemon available in this unprivileged container 2. No docker socket bind-mounted from host 3. dockerd --rootless fails: fork/exec /proc/self/exe: operation not permitted 4. containerd fails to extract layers: mount: operation not permitted 5. Cannot install packages via apt (no root) 6. Docker service explicitly not installed (no dockerd anywhere on system) tokens used 427,502
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 MIT, as reported by its host.
- Measured 2 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.
- Took 30 minutes to install, slower than the median of the 23 comparable projects Argusic has measured.
Of the 24 docker projects Argusic has installed and timed, All-jellyfin-media-server was the 21st fastest to reach a running state, and 16 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 | Did not run | 20.00 | 0.04 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 2.04 |
Topics (from GitHub)
dockerdocker-composefilmgluetuninstalljackettjellyfinjellyseerrmovies-hostingnordvpnplexproton-vpnprowlarrradarrself-hostedsonarrvideovpn
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/all-jellyfin-media-server)Questions
- Does All-jellyfin-media-server run?
- Argusic could not verify that All-jellyfin-media-server runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test All-jellyfin-media-server?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d0e84b8f7950. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test All-jellyfin-media-server?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does All-jellyfin-media-server take to install?
- 30 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 All-jellyfin-media-server need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing All-jellyfin-media-server?
- 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 All-jellyfin-media-server compare with the alternatives?
- Of the 24 docker projects Argusic has installed and timed, All-jellyfin-media-server was the 21st fastest to reach a running state, and 16 of 24 reached one at all.
- Where is the evidence for All-jellyfin-media-server?
- 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.