Skip to content

Clarify Docker watcher startup behavior #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lantiumBot merged 1 commit into from
Mar 21, 2026
Merged

Clarify Docker watcher startup behavior #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -231,6 +231,22 @@ docker compose up -d

Le service démarre avec la commande `-watcher`.

> **Note importante :**
> Le mode `-watcher` utilisé par le compose par défaut suppose qu'un client torrent configuré soit accessible si `-noseed` n'est pas utilisé.
> Si `qBittorrent`, `Transmission` ou `rTorrent` n'est pas encore joignable depuis le conteneur, le service peut redémarrer en boucle au lancement.
>
> Pour un premier test Docker sans client torrent, tu peux par exemple lancer :
>
> ```bash
> docker compose run --rm unit3dup -scan /watch -noseed -noup
> ```
>
> Ou modifier temporairement la commande du service en :
>
> ```yaml
> command: ["-watcher", "-noseed"]
> ```

### 5. Lancer un upload manuel

Pour envoyer un fichier déjà présent dans le volume `/data` :
Expand Down