No no - it’s not plagiarism; it’s standardization.

Leave it open and unsecured on the internet and see what happens

That is some big dick energy ngl

Self hosting isn’t likely to ever get to the point of “plug and play”. It’s inherently incredibly flexible and different people will do different things with it. Some people just want NAS. Some people want to build a router. Some people want to have a modest compute farm that they physically own. Some people want a virtualization playground. Or pretty much anything else you can think of, or some combination thereof.

For instance, I custom built a 2-tier + optane cached NAS running proxmox, and I have a handful of old thin clients I can spin up for doing Beowulf things when I feel like it, and I also have another repurposed thin client with an old enterprise-grade SFP+ NIC running pfSense as my router that can support up to 10g (futureproofing).

GSV, and thank you very much for noticing

Nothing, they’re just being an ass. Don’t worry about it.

No u

DAS enclosures are super easy to set up. Disk won’t be a big issue if you go that route.

If you’re planning on running containers, tbh I would not. The required virtualization layer (due to macOS being BSD-based) is going to make containers WAY less efficient. You’re better off with a system you can easily slap proxmox (or whatever distro floats your boat) on.

Huh, really? Is there that much of a perf hit using passthrough? I’d have assumed that the bottleneck isn’t actually the PCIE, so much as it is the beefiness of the GPU crunching the model.

Bro this is a community for sharing knowledge and increasing the technical aptitude of fellow users by doing said sharing. Maybe instead of shitting on a pretty solid digest of the fundamentals of setting up something like this, try adding to the body of knowledge instead.

Wtf are you talking about. PCIe passthrough exists.

Fair; I blame target fixation

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.

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.

+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