Last year I put on a TDD for Arduino workshop. Leaving a build tools image behind means I can just pick it up and work on it without spending a day getting back up and running. Without fail, when I come back to some old project, I've since updated my tools for something newer, and I can't build that old project without either upgrading the project or degrading my tools.
Not only is this great for teams, but it's also fantastic when you have side projects that you only periodically revisit. Then everyone, including your build server, uses that single pre-packaged image. Instead of everyone on the team needing to setup their development environments identically, and then keep them in sync, you define the build tools in a single place, a docker image.
I won't fault you for it.ĭocker is a great tool for deploying web services, but one of my favorite uses for it is standardizing toolchains. If you've been struggling with this issue and just want an answer, skip to the bottom for the TL DR.
