4 ms·
Out of curiosity, what kind of artifacts are you deploying and how are you building them?
by stfp 5y ago
Out of curiosity, what kind of artifacts are you deploying and how are you building them?
- hughrr 5y agoBuild in Jenkins. self-contained ReadyToRun .Net core apps. Couple of smaller Go apps. I rather like Go. Target package contains one file! Config is inherited from the environment and cloud provider as the targets are Amazon Linux 2 based.
- ecnahc515 5y agoCompiled executables are pretty simple to deploy without containers. The benefit of containers is that it can help standardize that type of benefit to other runtimes like Python/Ruby where it's much more challenging to just ship an artifact. In addition to that, with cgroups and namespaces you get a lot of other benefits, which can be used with eg: systemd/etc but it's nice when one tool handles all of it.
- hughrr 5y agoYes exactly. It's a solution to a problem. My point is it is better to avoid the problem than employ a solution.
- meowface 5y agoIt's not easy when the only way to avoid the problem you describe is to rewrite your whole project(s) in a language like Go. I like Go and have used standalone binaries instead of Docker containers when deploying Go applications, but I don't always work with Go applications. As other posters said, Docker largely exists to help with any situation where you don't have a single binary. These situations are still very common for many developers and devops engineers. And in those cases, Docker can be very helpful.