My First Time Using Docker — It Was a Disaster LOL

I’d heard the hype: “It works on my machine — now yours too!”
Docker was supposed to be magic. So I installed Docker Desktop, pulled an Ubuntu image (fancy, right?), and prepared to feel like a DevOps god.

Disaster hit in under 10 minutes.

Mistake #1: I ran docker run -it ubuntu and somehow expected my code to just… be inside. It wasn’t. I was staring at a bare Linux shell like “where’s my Node app?”

Mistake #2: I discovered volumes. Or rather, I didn’t. I copied files into the container manually, exited, and lost everything. Gone. Like a dream.

Mistake #3: Ports. I exposed 3000, ran my app, opened localhost:3000 — nothing. Forgot -p 3000:3000. Spent 20 minutes blaming Docker.

Mistake #4: Docker Compose. I wrote a YAML file, ran docker-compose up, and got indentation errors for an hour. An hour.

By midnight, my container was 5GB, I had 12 unused images, and my app still didn’t run.

The win? The next morning, I read the docs properly. Deleted everything. Started with a simple Dockerfile and one docker run -p. It worked.

That feeling? Worth the disaster.

Lesson: Docker has a cliff-shaped learning curve. You will fall off. But you’ll also climb back up — and laugh about it later.

Now I use Docker daily. But I’ll never forget that first night of glorious failure.