And then you are basically hiring an infra team to run the services and have the redundancy, and then with salaries you’re nearing just paying for software again

You’re looking for namespaces. Have a public and private namespace

I was just talking to a member of my devops team and I was talking about this exact thing and they said “I didn’t know you could attach a GPU to a container”. So, yup, just stay on top of this stuff at home and you’ll do fine

I’ll be honest man, just don’t do it. I tried, I really did, to make this exact scenario to work. You can get it to work - but it will be extremely brittle. You’re essentially hacking around LXC to do things it wasn’t built to do, and most of it is disabling security that’s there for a reason. At the end of the day you are essentially running docker directly on the host anyway, the passthrough lxc becomes less and less “there” vs passing stuff through. Then, every update to proxmox became anxiety riddled because every update would change or break something on my setup.

If you want to continue, more power to you, but I hope you heed my warnings. This is a path you will spend a lot of time on and experience a lot of frustration. Spin up a tiny debian VM and run the containers there, the overhead of the VM has been negligible, and any speedup I might have had has been made up 10x by cutting the amount of time I’ve had to hack proxmox to make it work.

the default is root, but most containers will specify a UID/GID to run under. That makes it even harder with docker on lxc on proxmox.

Sometimes yes, but I haven’t seen that lately. 5 years ago I had several of those, but I haven’t seen it recently

Weird for the UI to be crashing, it’s all javascript, once it’s loaded in your browser it’s loaded. Are there any extensions that are causing issues? Anything in the browser console? Network calls hanging?

Best buy wd elements. On sale every couple of weeks. Crack open the shell and you have a wd red or white.

Doesn’t freeze for me, what sort of hardware are you running it on?

There were some automod things built by 3rd larties, and they help, but it’s still a worry. There’s also image proxying now, so at least I’m not directly hosting it, but I’m not 100% that the feds will see it that way immediately

While I run my own Lemmy instance, I can say with 100% certainty - do not host a Lemmy instance on your own hardware.

It’s tempting, and I did, but don’t. The reason? CSAM. Your hosting stuff for other people, and if someone uploads something horrible to another instance, that is federated with you. That means now you are hosting that content.

The feds then have full rights to kick down your door and seize your hardware. On the cloud however, they’ll seize your VM , but your home stuff is okay.

Hosting Lemmy is great - but it’s something you really have to think about. Hosting your content is awesome, fun, and rewarding. I’ve learned hosting other people’s content is… Not as fun.

It’s so easy to set up, just tick a box during os install most times. Then if you do rcline just use an encrypt on top of your remote, make sure your conf is backed up, and you’re golden

Tried that once. It was not a fun route to go down. If let’s encrypt ever dies it anything fine, I’ll look into it again. Until then, let’s encrypt all the way

I’ve never really seen why portainer is used beyond a shiny UI. Docker compose file is enough for me

Yes, if you pass the gpu into the container

This is all over a GitHub stars badge? Developers probably want to encourage people to star it. It’s a huge stretch to say they’re trying to track people

Yeah it’s pricey, very pricey, but the risks are just too high for a home not to be properly grounded anymore. Homeowners have had 50 years to do it, it’s time to get it done.

I know that the answer is yes

I mean, there you go, and all of the above. I’d add in a pretty large fire risk too. I hear my battery backups kick in regularly, and we’re talking about enough power to equal a large appliance (at least in my case). It’s 100% worth it to move them to a grounded outlet.

Exactly right there with the not worrying. Getting started can be brutal. I always recommend people start without worrying about it, be okay with the idea that you’re going to lose everything.

When you start really understanding how the tech works, then start playing with backups and how to recover. By that time you’ve probably set up enough that you are ready for a solution that doesn’t require setting everything up again. When you’re starting though? Getting it up and running is enough

WD Red has always been my go-to, and in the last 8 years of homelabbing I haven’t had a single one fail. Blues and Greens are not build for NAS operations, and you’ll see them fail. Toshibas I haven’t had a single one make it past a year, except for their gaming drives.

If you want the shortcut, the WD Elements usually go on sale at Best Buy regularly, and they’re always a WD Red or White, which will also work. All of my drives have been one of those. You just shuck the internal drive out of the enclosure