Well sure, but the question was about gluetun, so I was trying to focus on that and the applications thereof. In terms of homelab stuff, I know a lot of people appreciate the containerized approach.
Well sure, but the question was about gluetun, so I was trying to focus on that and the applications thereof. In terms of homelab stuff, I know a lot of people appreciate the containerized approach.
Hahaha gottem
Oh yeah you can do it that way too, but if you want it all containerized, that’s roughly how to do it. That’s all I meant.
It’s convenient if you want to see gluetun up as the only way a container (say, your torrenting container) can get to the open net, in the interest of avoiding getting directly pinged by DMCA rats. That way, if the VPN goes down, your torrent client isn’t just downloading stuff nakedly. Also, if you want to set up different VPN connections for different containers, it’s pretty easy to set a handful of replica containers for that too.
Note that some issue devices have VT-x disabled and the bios locked down by Corp IT for one reason or another, so a VM may not actually be possible from the work issue device here.
Tbh, just run the Ubuntu box headless and ssh into it. You can do anything you’d need to. Even better, swap it to Debian or something like that, because Ubuntu is unfortunately kinda undergoing gradual enshitification lately.
I don’t mean to imply it’s perfect, but as a relatively popular distro to use as a daily driver, I’ve been happy with it overall.
Ubuntu is very much NOT the best of the distros anymore.
I’ve been using Kinoite on one of my daily drivers, and so far I’m loving it.
Again: name them. Describe the failures.
I simply don’t believe that you have 100% incompatibility, and I say that because I use a decently broad selection across several devices without any serious issues. Sure, they’re not perfect, but they’re a damn sight better than snaps, and in my experience, decently reliable.
Back your claims with data, or be prepared to have people like me call bullshit.
lol what are you talking about? One of my daily drivers is Kinoite and it works great. What flatpaks are you having issues with? Frankly, you must be being hyperbolic, because tons of people use tons of flatpaks without issue.
Yeah, I was not loving how hard they’re going for snaps, but the whole “Ubuntu Pro” bullshit scaremongering just 100% turned me off of the distro.
Just checked on my work box - if you go into Disk Utility and start the process to add a volume, the default selection is APFS
, and there’s an option in the dropdown for for APFS (Case-sensitive)
macOS also does this by default, but you can change it (though you have to reformat the disk in question). This is generally fine for non-system disks if you REALLY need it for some reason, but afaik it is not recommended for the OS disk due to assumptions that macOS-targeted binaries make (similar to the windows regex version matching that caused problems for a while because it became the unofficial best way to check windows versions for app install compatibility). It’s doubly annoying on newer Apple systems because the integrated SSDs are WAY faster than pretty much anything else you can connect to it. But for the most part, I find it’s more of a nuisance to keep in mind than a real problem (I’ve been dealing with dev-issue MBPs since about 2012).
As in the windows case, this is also an appropriate choice for the average Apple user (though the fact that they’re fairly ubiquitous as dev machines in many places is annoying on several levels, despite the generally solid best-case performance and thermals I’ve observed).
Nah it looks right to me
And the “R” stands for “reliable”, but your mom goes down every night so I’m not sure what that’s supposed to be about
+1 - GL.iNet is cheap as hell and perfectly functional. It runs DD-WRT under the covers, and it’s super easy to “unlock” the full powers of the distro (literally a toggle in the basic ui, iirc). Used it on a longer trip my partner and I took a few months ago, and it was great! On-device storage is paltry, but, well, that’s not what it’s for.
deleted by creator
For SSDs, enterprise-tier drives typically set aside a lot more dedicated space for wear management. So in many cases, it’s actually a 1TB (or 2 -> 1.8T, etc) drive, but the disk controller/firmware only allows addressing a subset of the “true” capacity.
Fair; I blame target fixation