![](https://doomscroll.n8e.dev/pictrs/image/70f50cc7-420f-4881-bc24-eb1af0d92cdb.webp)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
blocked part of url because I have Kagi rewrite url to redirect to my private Redlib instance
I had no idea this was a thing. Thats going straight on my self-host todo list.
blocked part of url because I have Kagi rewrite url to redirect to my private Redlib instance
I had no idea this was a thing. Thats going straight on my self-host todo list.
It’s the multiple volumes that are throwing it.
You want to mount the drive at /media/HDD1:/media
or something like that and configure Radarr to use /media/movies
and /media/downloads
as it’s storage locations.
Hardlinks only work on the same volume, which technically they are, but the environment inside the container has no way of knowing that.
Documentation people don’t read
Too bad people don’t read that advice
Sure, I get it, this stuff should be accessible for all. Easy to use with sane defaults and all that. But at the end of the day anyone wanting to using this stuff is exposing potential/actual vulnerabilites to the internet (via the OS, the software stack, the configuration, … ad nauseum), and the management and ultimate responsibility for that falls on their shoulders.
If they’re not doing the absolute minimum of R’ingTFM for something as complex as Docker then what else has been missed?
People expect, that, like most other services, docker binds to ports/addresses behind the firewall
Unless you tell it otherwise that’s exactly what it does. If you don’t bind ports good luck accessing your NAT’d 172.17.0.x:3001 service from the internet. Podman has the exact same functionality.
But… You literally have ports rules in there. Rules that expose ports.
You don’t get to grumble that docker is doing something when you’re telling it to do it
Dockers manipulation of nftables is pretty well defined in their documentation. If you dig deep everything is tagged and natted through to the docker internal networks.
As to the usage of the docker socket that is widely advised against unless you really know what you’re doing.
I work for the UK government. Everything my organisation does is licensed in either MIT or OGL (https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/)
Developing code in the open really helps ensure you nail down your secure coding practices.