One of the things I care deeply about is helping other engineers grow. Over the last year, I’ve had a lot of conversations, some with folks just entering the field, others with seasoned pros, asking the same question: how is AI going to reshape our work? There is fear and uncertainty, but also some optimism.

There’s a rhythm to these tech cycles.

I’ve seen it before, big promises, huge hype, sweeping predictions. Right now, we’re being told that AI will replace entire roles, maybe entire industries. It’s the same energy we saw with self-driving cars. For years, we were told they were just around the corner. But today, in 2025, I still don’t see a 40-ton truck rolling down the Autobahn without a driver. Waymo works, yes, but in tightly controlled areas, in a few cities. Meanwhile, here in Europe, truck drivers are still very much in demand.

If you’ve been in the container game for a while, you’ve probably seen a lot of buzz around “distroless” containers. The first time I heard the term, I pictured a container floating off into the void - no OS, no shell, just… code. Turns out, that’s not too far from the truth, but just like Serverless, Distroless is a misleading term!

Let’s break down what distroless containers are, why you might want them in your stack, what they’re great at (and not-so-great at), plus how to actually debug one.

Over my two decades as an infrastructure engineer, I’ve watched our field transform dramatically. What began with manual server configuration has evolved into defining entire organizations infrastructure as code. This journey reflects not just technological change, but a complete shift in how we approach managing systems at scale. I’ve been in the trenches through most of it, and I want to share my story of this evolution with fellow infrastructure engineers who’ve lived through similar transitions.