Docker

The first time I ever built a Docker image, it worked. The container started, port mapped, and the app responded in the browser. But if I’m being honest, I couldn’t clearly explain what happened between docker build and seeing that response. I understood the commands, but I did not fully understand the flow. In this write-up, I will walkthrough a small application from source code to a running container on a remote server and explain what is happening at each stage. ...

Docker changed what I consider worth setting up. Without containers, trying new software usually means committing to an environment: Pick an OS. Install dependencies. Open ports. Configure access. Hope you remember what you did the next time you come back. Even when the goal is just to try something, the setup feels heavier than the thing you’re actually interested in. The cost in time adds up, now you’re more hesitant to fire up the service or tool. ...

I’m rebuilding part of my AWS setup and figured this was a good time to write this down instead of relying on memory and vibes. Any time I need a clean Docker environment to test images or mess around without breaking anything important, I really don’t want to be clicking through the AWS console or babysitting a server. The problem is always the same. I need an Ubuntu box, Docker installed, basic access set up, and I need it quickly. Doing this manually means clicking through EC2, setting up security groups, opening ports, SSH’ing in, installing Docker, and then deciding what to do with the instance when I’m done. ...