this post was submitted on 26 Nov 2025
36 points (95.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
65391 readers
163 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
🏴☠️ Other communities
FUCK ADOBE!
Torrenting/P2P:
- !seedboxes@lemmy.dbzer0.com
- !trackers@lemmy.dbzer0.com
- !qbittorrent@lemmy.dbzer0.com
- !libretorrent@lemmy.dbzer0.com
- !soulseek@lemmy.dbzer0.com
Gaming:
- !steamdeckpirates@lemmy.dbzer0.com
- !newyuzupiracy@lemmy.dbzer0.com
- !switchpirates@lemmy.dbzer0.com
- !3dspiracy@lemmy.dbzer0.com
- !retropirates@lemmy.dbzer0.com
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A bit off-topic, but, anyone else having issues with the Lidarr docker container refusing to boot? Had it working a few months ago now after updating the image i get "port already in use" errors in the logs? Is it just my setup or did something break upstream?
I'm not using it atm, but you probably are running another service on the same port. Try mapping lidarr to a different port.
Mine runs fine.
Maybe your container port is actually in use?
I checked and there doesnt seem to be anything running on that port, i closed a working container on another port and tried running it on that one but it still errored out. Hence why i thought it wasnt on my side.
I'll have to do some more digging it seems...
Maybe try enabling debug logs inside the container through a config file (if that is possible)