July 15, 2026
Cluster drama goes domestic
Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes
After one cursed basement server, the internet cheers a simpler home setup
TLDR: After a disastrous home server kept failing, the author ditched the complicated setup and rebuilt around simpler tools they can manage alone. Commenters mostly cheered the move as common sense, though a few insisted the much-maligned system works great if you know what you're doing.
A home tech tinkerer just posted the kind of breakup story the internet lives for: after a year of server chaos, mystery crashes, and one allegedly cursed machine nicknamed nibbler, they finally dumped the complicated setup and went back to something simpler they can actually keep running. Translation for normal people: instead of using a giant, enterprise-style control system meant for huge fleets of computers, they chose a more straightforward way to run apps at home. And the comments? Oh, they had feelings.
The loudest reaction was basically: "finally, someone said it." Several commenters piled on the idea that this heavyweight tool is just too much for one person with a day job and a life. One user flat-out agreed with the author’s confession that it was too hard to maintain unless the whole point of your hobby is learning that tool. Another cheered the return to simpler methods, while one amused commenter admitted they still don’t even know what the system is for outside very specific situations — but hey, they were delighted by the surprise appearance of Ruby, the programming language. The author even jumped in to calm the mob, saying this wasn’t meant as anti-tool propaganda, just a reality check from someone who got tired of babysitting broken gear.
But not everyone joined the anti-complexity parade. One dissenter was genuinely shocked by all the hate, insisting their own three-machine setup has been rock solid and easy. So yes, the thread turned into a classic internet brawl: Team “keep it simple,” Team “you’re using it wrong,” and everyone bonding over the most relatable villain of all — a bad eBay purchase that turned a dream machine into basement melodrama.
Key Points
- •The article is a follow-up describing how the author rebuilt a homelab after major hardware failures and an abandoned Kubernetes project.
- •Of the original cluster machines, only lrrr remained operational, while nibbler—originally a Lenovo M80s Gen3 SFF configured as the core server—proved unreliable and caused repeated storage failures.
- •The author observed boot problems, disappearing hardware, and SAS adapter driver errors on nibbler, and believed the machine may have been sold in faulty condition despite a refurbished label.
- •The homelab was simplified by moving important services off Kubernetes and back to Docker Compose.
- •By July 2026, the setup included lrrr running Proxmox, morbo running TrueNAS SCALE for storage, a Chicago-based ingress VM called ord-router, and a rebuilt nibbler with a Ryzen 9 9900X and RTX 5060 Ti for local LLM experiments.