yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

e2e is permanently red on main: a leftover qBittorrent container blocks every run #269

New Issue
Open
opened 2026-08-30 11:58:16 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-30 11:58:16 +01:00
Owner
Copy Link
Copy Source

The qBittorrent step of .gitea/workflows/e2e.yml starts the container with a fixed name and no cleanup:

docker run -d --name arr-e2e-qbittorrent --network host ...

There is no --rm and nothing removes it beforehand, so once a run leaves the container behind, every later run dies at that step:

docker: Error response from daemon: Conflict. The container name
"/arr-e2e-qbittorrent" is already in use by container "f4212de4a2fd...".
exitcode '125': failure

The step is before build daemon, so no test executes and the failure says nothing about the commit under test. First seen on run 1549 (commit 6cd2902); it will now fail on every push to main until the container is removed.

Introduced with the Transmission-to-qBittorrent swap in ab4f95b — the Justfile e2e-up recipe passes --rm, the workflow does not.

Fix: remove any existing container before starting, e.g. docker rm -f arr-e2e-qbittorrent 2>/dev/null || true, and stop it in an if: always() step so a cancelled run does not leak one either.

The `qBittorrent` step of `.gitea/workflows/e2e.yml` starts the container with a fixed name and no cleanup: ``` docker run -d --name arr-e2e-qbittorrent --network host ... ``` There is no `--rm` and nothing removes it beforehand, so once a run leaves the container behind, every later run dies at that step: ``` docker: Error response from daemon: Conflict. The container name "/arr-e2e-qbittorrent" is already in use by container "f4212de4a2fd...". exitcode '125': failure ``` The step is before `build daemon`, so no test executes and the failure says nothing about the commit under test. First seen on run 1549 (commit 6cd2902); it will now fail on every push to main until the container is removed. Introduced with the Transmission-to-qBittorrent swap in ab4f95b — the `Justfile` `e2e-up` recipe passes `--rm`, the workflow does not. Fix: remove any existing container before starting, e.g. `docker rm -f arr-e2e-qbittorrent 2>/dev/null || true`, and stop it in an `if: always()` step so a cancelled run does not leak one either.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#269
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?