What you’re describing sounds pretty much exactly like how I use Proxmox at this point (everything in LXCs, most just running docker on Alpine) and I’ve been wanting to make the switch to Incus for a while. Did you migrate your LXCs over from Proxmox? I’m a little worried about how painful that process might be.
He’s always been a deceitful and manipulative narcissist, even before being an industry plant anti-consumer shill.
Here’s a good one, the time he manipulated someone a decade younger than him for money and sex via furry roleplay while hiding the fact he was married: https://piratesoftware.sucks/
Checks out, if you’re a Gnome user you’re already used to being told how you should be doing things by them.
I agree, but they’ve also made deliberate moves to muddy the waters of open source and push the limits of what is acceptable under GPL, and I’m not going to shed any tears over their loss of potential corporate profit.
Dude you’re fighting a very uphill battle trying to make us feel bad for an IBM subsidiary.
I think the risk of losing data naturally leads to people seeking out the most robust storage solution possible when 90% of those people would probably be better off with something simpler with less that can go wrong.
I can’t answer each bullet (and a couple are dependant on other things like drive speed, activity, and network throughput) but I’ve been using shucked external HDDs for over a decade and would recommend it. I used to use OpenMediaVault running in a VM on Proxmox and briefly tried TrueNAS, but I’ve since migrated all of my VMs to LXCs, so now I just have the drives mounted on the Proxmox host directly combined with mergerfs (not managed by Proxmox’s storage pools) and I pass it through to a Turnkey Linux file server LXC via bind mounts to share over SMB/NFS. Less overhead and LXCs can share CPU/memory dynamically while VMs can’t.
You should be able to replace that /mnt/external directory with no issues as long as the structure is the same within.
I don’t think you realize that if your goal is to have a simple install method anyone can use, even redirecting the output to install.sh like in your examples is enough added complexity to make it not work in some cases. Again, those are not made for people that know bash.
If you can’t review a bash script before running it without having an unnecessarily complex one-liner provided to you to do so, then it doesn’t matter because you aren’t going to be able to adequately review a bash script anyway.
Showing people that are running curl piped to bash the script they are about to run doesn’t really accomplish anything. If they can read bash and want to review the script then they can by just opening the URL, and the people that aren’t doing that don’t care what’s in the script, so why waste their time with it?
Do you think most users installing software from the AUR are actually reading the pkgbuilds? I’d guess it’s a pretty small percentage that do.
That reddit thread is horrible advice, it’s just mapping the LXC root user to the host root user, which is just a privileged LXC with extra steps (and maybe less secure).
The reason you’re probably having issues is that your root user in the LXC is mapped to the host user 100000 by default, and that user doesn’t have access to the share, but you can change that with mount options or creating a user with 100000:100000 and adding it to a group with access.
I use Tautulli, but I’m not sure if that is going to cover all the same use cases.
I haven’t gotten around to spinning it up yet, but I was just looking into this myself and was going to try out Pinchflat. If anyone has used it and has any feedback I’d love to hear it.
I was between it and Tube Archivist.
For anything. You can get a push notification for anything you can make run a script or send an http request.
This has strong “nobody needs a monitor over 120Hz because the human eye can’t see it” logic. Transparency is completely subjective and people have different perceptions and sensitivities to audio and video compression artifacts. The quality of the hardware playing it back is also going to make a difference, and different setups are going to have a different ceiling for what can be heard.
The vast majority of people are genuinely going to hear zero difference between even 320kbps and a FLAC but that doesn’t mean there actually is zero difference, you’re still losing audio data. Even going from a 24-bit to a 16-bit FLAC can have a perceptible difference.
Nobody “needs” to listen to music over Bluetooth at all, but why not make it sound like it’s supposed to?
Just run docker in an LXC. That’s what I do when I have to.
I’m not really worried about it. Each LXC runs as its own user on the host, and they only have access to what they need to run each service.
If there’s an exploit found that makes that setup inherently vulnerable then a lot of people would be way more screwed than I would.
I don’t have anything publically accesible on my network (other than wireguard), but if I did I’d just put whatever it was on its own VLAN, run a wireguard server on it, and use a VPS as a reverse proxy that connects to it.
I only use unprivileged LXCs and everything I host on my network runs in its own LXC, so I’m not really worried about someone getting access to the host from there.
Bitwarden caches your vault to your device, so you don’t actually need a live connection to the server.