4 ms·
Unsurprising reasons for everything - security department would have been reluctant to allow development from inside AWS, and running in Docker was to ensure ev
by jamesfinlayson 4y ago
Unsurprising reasons for everything - security department would have been reluctant to allow development from inside AWS, and running in Docker was to ensure everyone (i.e. all developers, testers and TeamCity agents) were running on the same versions of runtimes etc (Docker was chosen as the easiest solution for this problem at the time).
- scarface74 4y agoDamn, I first got into AWS not just to avoid administering systems. But to also avoid system administrators. That being said, how do you get on different versions if everyone uses the same package manager config file (requirements.txt/package.json/the wonderful system that Go uses/whatever Nuget/C# uses). I’m also spoiled because I’ve never been in a position where I wasn’t the developer and leading the “DevOps” initiatives since working with the cloud - not bragging, I only opened the AWS console four years ago for the first time. HN/Reddit is a good place to find out other peoples experience.
- jamesfinlayson 4y agoIt's more to make sure everyone is using Java 11.x, Java 17.x, Python 3.x, Node x etc - we're on Macs but TeamCity agents are Linux and Docker is easy way to pin the runtime on both operating systems. Docker also fixes the "I forgot to brew install a specific version" in this case.