My hotest selfhosting take is that stuff I use in my day job, docker/k8s/cloud is not worth it and generally worse for long-term self hosting than a Debian box.
Like I have the skills to troubleshoot containerized setups, it’s litterally my dayjob, but I’d rather not deal with it in my freetime unless there is no other way to run it.
Is that a hot take? I see a lot of people saying this, including myself. Kubernetes solves problems at work, but is way overkill even for my moderately elaborate home setup that would cause more troubles than it solves. If people want to use k8s at home go ahead, but I don’t.
Honestly, I’m really happy with the ability to just try out stuff with docker and then nuke the entire compose stack if it does not work. I also know perfectly where any possible leftovers from the attempt are (the bind mounts or volumes) and can be certain I deleted everything I “installed”.
Although I have to admit that I absolutely had some issues with containers in the past, mainly when there are two or more containers with dependencies on one another
ohshit604@sh.itjust.works 1 day ago 
lol
RIotingPacifist@lemmy.world 1 day ago
My hotest selfhosting take is that stuff I use in my day job, docker/k8s/cloud is not worth it and generally worse for long-term self hosting than a Debian box.
Like I have the skills to troubleshoot containerized setups, it’s litterally my dayjob, but I’d rather not deal with it in my freetime unless there is no other way to run it.
sandwichsaregood@lemmy.world 1 day ago
Is that a hot take? I see a lot of people saying this, including myself. Kubernetes solves problems at work, but is way overkill even for my moderately elaborate home setup that would cause more troubles than it solves. If people want to use k8s at home go ahead, but I don’t.
esc@piefed.social 1 day ago
k8s is overkill for majority of companies as well
Allero@lemmy.today 23 hours ago
After using Proxmox for a while, I swear by LXC, at least the way it is provided there.
Makes containerization make sense without all the pain.
Scrath@lemmy.dbzer0.com 20 hours ago
Honestly, I’m really happy with the ability to just try out stuff with docker and then nuke the entire compose stack if it does not work. I also know perfectly where any possible leftovers from the attempt are (the bind mounts or volumes) and can be certain I deleted everything I “installed”.
Although I have to admit that I absolutely had some issues with containers in the past, mainly when there are two or more containers with dependencies on one another