Anyone else found Docker very fun to learn and you’re constantly looking for ways to use it at work?

My department is quite outdated in terms of our CI/CD processes, not at any fault of their own but rather due to our dependence on some off-the-shelf software in our stack. As a result, a lot of my fellow team members take a ton of time to test their changes locally due not having stubs/mocks setup. As a result, I took on learning Docker.

While I'm still a junior at Docker, I've been evangelizing it around different teams I work with and offering to dockerize their apps. I even unearthed the "for home projects" Raspberry Pi that was tucked away in my junk drawer and set it up with docker containers as a homelab/PiHole server and for some of my personal projects.

I'm definitely late to the game here but it's honestly one of the best new skills I've picked up this year.

11 thoughts on “Anyone else found Docker very fun to learn and you’re constantly looking for ways to use it at work?”

  1. It’s easy to see Docker as your hammer and every problem a nail. Don’t evangelize it – it’s a tool in your toolbox and it’s not suitable for every problem. There are other ways to run containers as well and sometimes a container isn’t even the right solution at all.

  2. You can use a docker container in Kubernetes. Which I find to be a better solution than pure docker. You can spread your load out across multiple servers and have scalability. That web site you have up is not responding very fast, scale up the number of pods and it will load balance within itself. It only gets hammered during the 2nd of every other month, setup a cron job to scale it up for a week and then scale it back down after that. Now you have automated your peak times and don’t have to manually do anything with it.

    Since they are all tied to the same persistent storage they will always look the same and function the same and your end user won’t even know.

    Like others have said, it is a tool and not everything can/should be a container. I wouldn’t try to containerize a mail server for a company, but I would for personal.

  3. About two years ago when I needed to learn Docker solidly, I spent a few weeks taking my Linux serve at home, that had about a dozen different services running (MySQL, GitLab, etc.) and migrated them all to containers instead of running on bare metal. I had to deal with the network issues, getting them to talk to each other, mapping to host mounts so I could back up. I also learned Ansible in the process since I built a playbook that could rebuild everything from scratch if needed. It was a phenomenal learning experience.

    But, it’s a little addictive because now I just go browse Docker Hub looking for cool new things to install just for fun 🙂 I’ve also since migrated to a VM on my primary server, so now I have 20+ Docker containers running in the VM (which has its own challenges).

    I definitely recommend such an exercise if you just want to play. A repurposed old machine is all you need.

  4. As a software architect, I *really* despise situations in which tools are chosen because they’re someone’s favorites versus good fits for their intended use cases.

    It routinely makes things both more difficult and costs clients (I’m a consultant) large amounts of money.

    Docker/containerization is a very good tech. It makes sense in some cases. It does *not* make sense in all cases and shouldn’t be shoehorned/forced in to tech stacks without consideration.

  5. Yes!
    Messed with it a few times the last couple of years but the last couple of weeks I’ve dived deep into the docker hole. Looking for more things I can run to sup lime to what I already have and just add new things because it’s fun. Like Lego blocks


Leave a Comment