Prologue: The Call to Adventure

I've watched a lot of kids fall down the tech rabbit hole over the years. Usually starts the same way—they want something, and nobody's around to show them how to get it.

Max Power was no different. Twelve years old, too smart for his own good, bored out of his mind in school. The kind of kid who gets C's in classes he doesn't care about and accidentally aces the ones that catch his attention. His teachers keep saying "not working to potential," and he's heard it so many times the words don't mean anything anymore.

But Minecraft? Minecraft had his attention.

Here's the thing about Max—he's not just dreaming. He's the kind of kid who actually tries stuff. Downloaded Minecraft mods before, messed around with resource packs, got pretty good at redstone. But running an actual server? That felt like dark magic. The kind of stuff you need a computer science degree for.

Or at least, that's what he thought.

Max had tried the obvious stuff. Realms worked, technically—but it cost money every month, and more importantly, you couldn't really mod it. Just whatever Microsoft decided to put in the Marketplace. Paid add-ons. Boring.

He'd heard about "dedicated servers" but every guide he found was either for Java Edition (his friends all played Bedrock on their phones and Switches) or assumed you already knew what Linux was. Which he didn't.

And there was another problem.

So Max was stuck. He wanted a server his friends could actually connect to, running on something that wasn't his dad's work laptop, with the ability to install whatever he wanted on it.

That's when his dad mentioned me.

I've known Max's dad since college. We were roommates sophomore year, back when the internet ran on dial-up and "cloud computing" meant the weather forecast. I've watched Max grow up, babysat him when he was little, taught him his first card game.

And apparently, I was now his best shot at getting a Minecraft server running.

Max's dad called me on a Tuesday. "Hey, Max has this... project. Something about Minecraft. I told him you'd know about this stuff."

I could hear Max in the background: "Tell him about the MODS, Dad. The mods are the whole point."

Kid had done his homework. Sort of. He'd found the right rabbit hole—he just didn't know how to go down it yet.

"Docker, huh?" I said. "Where'd you hear about that?"

"Some guide for running a Bedrock server. It said to use Docker but I don't know what that means and I don't want to break anything."

And there it was. The fear. The same fear I've seen in junior developers, in interns, in career-changers learning to code for the first time.

I don't want to break anything.

Here's what I told Max:

"What if I told you there's a way to run stuff on your computer where you literally can't break anything? Like a test world in Minecraft—you can blow it up, delete it, start over, and your actual computer doesn't care."

Silence on the other end. Then:

"That's exactly what Docker is, kid. It's like having infinite test worlds for software. Break one, delete it, try again. Your real computer stays safe."

I could practically hear the gears turning.

That was the moment. That's always the moment—when the fear of breaking things gets replaced by the excitement of building things.

Max didn't know it yet, but he was about to accidentally become a DevOps engineer.

I won't lie to you—you're going to break things along the way. Containers will crash. Data will get lost (we'll fix that). You'll type commands wrong and get error messages that seem personally insulting.

That's all part of it. Every single person who's ever run a server has been exactly where you are right now. The only difference between them and you is that they kept going.

Ready to start?