Infrastructure complexity (Kubernetes, Docker, YAML)

One reason I think a distinction is made is that native Docker-in-Docker can be a real pain, but Docker in a Firecracker microVM "just works".

sudb · Oct 3, 2026 · comment in “Docker has always used microVMs (well since 2016)”

Their goal is to create a system that's easy to run and manage even if you don't really know much about k8s - which I guess is a common thing, since k8s is a nightmare to manage directly until you learn everything about everything.

danudey · Oct 1, 2026 · comment in “Red Hat being phased out of existence?”

Tags for t-shirt sizes to set the amount of CPU/memory allocated to each job container. Maybe running on Kubernetes or some autoscaling solution is more painful.

tikkabhuna · Aug 17, 2026 · comment in “Ask HN: Alternatives to GitHub”

And if you thought the GitHub actions hybrid mix of JavaScript templates embedded in yaml was a nightmare, I have bad news for you with respect to ADO pipeline configuration documents...

baby_souffle · Aug 7, 2026 · comment in “GitHub Actions and Pages are experiencing degraded availability”

If anything, it helped keep my stuff alive during all the hardware issues a lot longer. I think like 5-6 years ago, kubernetes on baremetal was pretty painful.

MisterKent · Jul 16, 2026 · comment in “Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes”

Vagrantfile and OS agnosticism are not why I built virtdev. Vagrant has no security focus at all, and I explicitly opted out of declarative YAML because GitHub Actions is painful enough.

matheusmoreira · Jul 13, 2026 · comment in “Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop”

My only experience with VMs on macOS is colima+docker, and it's relatively painful and inefficient (but usable).

mgaunard · May 2, 2026 · comment in “How fast is a macOS VM, and how small could it be?”

On the other hand, I had to debug a PHP app in Docker using XDebug and it was mostly painless. Or, to be more precise, no more painful than debugging it on local Wamp/Xampp.

inglor_cz · Apr 22, 2026 · comment in “Laws of Software Engineering”

1. Parallelization: two tasks that both touch your Docker config or the same infra files are painful to run locally at once, and manual port rebinding and separate build contexts don't scale past a couple of tasks.

danoandco · Apr 10, 2026 · story in “Launch HN: Twill.ai (YC S25) – Delegate to cloud agents, get back PRs”

The same calls, with the same parameters, will often randomly fail with HTTP 400 errors, only to succeed later(hopefully without involving support). That made provisioning with terraform a nightmare.

outworlder · Apr 3, 2026 · comment in “Decisions that eroded trust in Azure – by a former Azure Core engineer”

the docker side of this is painful too. every extra dependency in any language means a bigger image, more layers to cache, more things that can break during a multi-arch build. ive been building images that are 4GB because of all the node and python tooling bundled in. micro packages make it worse because each one adds metadata overhead on top of the actual code.

CoderLuii · Mar 22, 2026 · comment in “The three pillars of JavaScript bloat”

Running untrusted code, random tools from the internet, or AI agents directly on your machine is an increasingly real risk. Containers are the obvious answer, but spinning up isolated shell sessions with raw Docker commands every time is painful enough that most people just don't bother.

mr-leshiy · Feb 17, 2026 · comment in “[dead]”

The shift from docker to podman was originally quite painful at first, but it's much better, very usable, and quite stable now.

esseph · Dec 18, 2025 · comment in “Systemd v259”

I think we are having different contexts here. I am mostly talking about selfwritten services and how writing, maintaining and deploying helm charts for them is a nightmare.

buster · Nov 14, 2025 · comment in “Helm 4.0”