Three months had passed since Max started this journey. The Minecraft server was humming along. His friends played every evening. Jake had rebuilt his castle twice (each time bigger). Emma had constructed an entire underground city. The CI pipeline caught Max's mistakes before they caused problems.

Everything was working.

Then one day, Max's laptop started running slow. Really slow. He texted me in a panic.

I had a pretty good guess.

"Open a terminal," I said. "Let's see what Docker's been hoarding."

"Remember all those times you experimented? Tried different images? Pulled new versions? Docker keeps everything unless you tell it not to."

I pointed at the screen. "See those numbers? You have 4.8 gigabytes of images, but only 1 is actually being used. The rest are taking up space for no reason. Same with containers—17 exist, but only 1 is running."

"Docker is like a digital packrat. It never throws anything away on its own."

"Let's look at what's actually there," I said.

"Nope. docker stop stops a container. docker rm removes it. Without that second step, they just sit there, taking up space and cluttering your list."

"Same with images. Let's look."

"See those <none> entries? Those are called 'dangling images'—leftover layers from builds that didn't complete cleanly, or old versions that got replaced. They're safe to remove."

"And those multiple alpine versions? You probably only need one."

"Let's start cleaning. The safest place to begin is stopped containers."

"Docker's prune commands always confirm first. It's a safety net. You can skip the confirmation with -f for scripting, but be careful with that."

"That removed the <none> images—the ones without names. But what about all those old alpine versions you don't need anymore?"

"rmi means 'remove image.' You can use the image name or the ID. Docker will complain if the image is still being used by a container—that's another safety net."

"Sometimes you just want to start fresh. There's a command for that."

"Notice what it doesn't touch: volumes. Docker protects your data by default. Your Minecraft world is safe."

"If you really want to remove unused volumes too—which you almost never do—you can add --volumes. But that's genuinely dangerous."

"Let's talk about volumes specifically. They're the most important thing to be careful with."

"That happens. Every time you use -v with a new volume name, Docker creates it. The volume persists even after the container is gone."

"Let's see what's actually being used."

"That's a bit arcane, but it shows which volumes are mounted to containers. Anything not in that list is probably safe to remove—but check first!"

"To remove a specific volume:"

"The prune command will only remove volumes not attached to any container—running or stopped. But if you've removed the container, the volume is fair game. Be sure you don't need that data."

"Cleaning up manually works, but it's easy to forget. Real operators automate this."

"Now let's schedule it to run automatically. We'll use cron—the classic Unix scheduler."

"One more thing," I said. "Good operators don't just clean up—they monitor. A quick health check script can catch problems before they become emergencies."

Max ran the script. Everything looked healthy.

"You could schedule this to run daily and email you the results," I said. "Or log to a file and check it when you remember. The point is: know the state of your system."

I leaned back in my chair. Max had come a long way.

"You know what you've learned over these past few months?"

"You've learned DevOps."

I let that sink in.

"Think about it. You started with a simple goal: run a game server. Along the way, you learned:

• Containers: How to package and run software reliably
• Volumes: How to persist data that matters
• Compose: How to orchestrate multiple services
• Scripts: How to automate repetitive tasks
• Git: How to track changes and undo mistakes
• CI/CD: How to make robots check your work
• Maintenance: How to keep systems healthy long-term

That's not just 'running a Minecraft server.' That's operating infrastructure. Real companies pay people good money to do what you just learned."

"You know the foundations. There's always more to learn—networking, security, scaling, monitoring at scale—but you've got the mindset. Automate the boring stuff. Save your work. Keep things tidy. Experiment without fear."

"Those principles work whether you're running a game server or a billion-dollar cloud platform. The scale changes; the thinking doesn't."

"So what now?" Max asked. "Is that it?"

"That's Volume 1. Your server is running, your friends are playing, and you're not afraid of the terminal anymore. But there's more."

"For now, though? You've got everything you need. Your server works. Your automation handles the boring stuff. Your Git history protects your work. Your CI catches your mistakes."

"Go play Minecraft with your friends. You've earned it."

"That's the secret," I said. "Learning's always more fun when you're building something you care about. The Minecraft server was never really the point—it was the excuse."

Max grinned and headed for his laptop. A few seconds later, I heard the familiar loading music.

Some things never change.