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.
Very first line of the GitHub readme. As a support tool it’s mostly useless, endless similar or identical questions answered differently or not at all and none of it indexed by search engines for use on the web.
It’s an awful data silo / black hole that increases volunteer load.
I’ve not used dockge so it may be great but at least for this case portainer puts all the stack (docker-compose) files on disk. It’s very easy to grab them if the app is unavailable.
I use a single Portainer service to manage 5 servers, 3 local and 2 VPS. I didn’t have to relearn anything beyond my management tool of choice (compose, swarm, k8s etc)
With a small amount of effort and the use of https://github.com/nanos/FediFetcher and https://github.com/g3rv4/GetMoarFediverse you can mitigate basically all those issues. It’s still not perfect by any means but it results in a perfectly usable single user instance.
The first populates the replies of the home timeline posts you see (as well as profiles of people it finds in those replies) and the second pulls down all the content from instances you select for your followed hashtags (choose mastodon.social and you can guarantee you’ll see most all posts with those tags)
IIRC your data would live on your chosen pod server - which does not have to be a fediverse instance.
Gonna go with… whoosh
If buying isn’t owning then piracy isn’t stealing.
Didn’t even think 4k80 was generally available yet?
There’s a couple of caveats with it, but I think neither are worse than your proposed flow.
Immich does support folders?
https://immich.app/docs/administration/storage-template/
With this you can store your photos in whatever structure you want.
Yes.
Docker will have only exposed container ports if you told it to.
If you used -p 8080:80 (cli) or - 8080:80 (docker-compose) then docker will have dutifully NAT’d those ports through your firewall. You can either not do either of those if it’s a port you don’t want exposed or as @moonpiedumplings@programming.dev says below you can ensure it’s only mapped to localhost (or an otherwise non-public) IP.
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.
Did someone manage to grab the flatpak in a usb installable format? It’s no longer on flathub, boo.
I think thats radicale
Each devices encryption keys are unique and non-transferable. Each message in a conversation is encrypted in such a way that every participating device at the time of sending can decrypt it.
New devices (like desktop clients) didn’t have their keys used for old messages and so can’t decrypt them. There is no way to reencrypt old messages with additional new keys.
It’s both annoying as shit, and also the only way to ensure a bad actor can’t just add themselves to conversations they weren’t a part of.
He only wins internet clout if you know who he is. I didn’t. He was just that guy in the meme.
Now he’s been named at least two people, who didn’t know of his existence, now know.
You’ve just Barbara Streisand’ this guy.
There’s a huge amount of it on the fediverse right now. People are working very hard at getting rid, all of them volunteers, and in their own time.
On my Pixel I long press at the bottom and then press on the code. I think it’s called google lens or something.