3 ms·

Ops here, bored is good. Bored means it's working properly and it's a solved problem. Also, I haven't seen a good alternative outside ConfigMgr like Puppet/Chef

Ops here, bored is good. Bored means it's working properly and it's a solved problem. Also, I haven't seen a good alternative outside ConfigMgr like Puppet/Chef/Ansible or something like Nix which has another set of problems. Containers work well enough and their positives vastly outweigh negatives in most cases. It's also a solvable problem for most part. If you have a set of packages almost all the software needs, someone should probably create base image for everyone with everything pre-installed so your dockerfile starts with FROM companybaseimage:latest

amelius 2y ago
> Ops here, bored is good. Bored means it's working properly and it's a solved problem. It's not a solved problem because build systems keep breaking in random places. Granted, these problems are in general easy to solve. But we're talking about death from a thousand papercuts here. In other words, boredom from a thousand compile errors.
- stackskipton 2y ago
  :shrug: Thousand compile errors sounds like Dev Team hasn't buckled down and fixed their build script (Dockerfile). Maybe they should take some time and do that. Other beauty about containers is ability to build in environment Devs control and any changes to build servers shouldn't impact them.
  - amelius 2y ago
    Perhaps you have never been in the situation where one package forces you into a particular version which in turn forces its dependencies to versions, etc., eventually pushing you into an impossible situation. Anyway, I wish I had a Dev Team like you have to solve these problems for me ...
    - nyrikki 2y ago
      If you aren't leveraging the namespace abstraction of containers, why use them at all? Noting that I am being frank and honest here, but you don't have a dev problem here, but most likely an organization level problem. Namespaces and interface contracts should be dramatically reducing dependency issues, not causing them to explode.

amelius 2y ago

> Ops here, bored is good. Bored means it's working properly and it's a solved problem. It's not a solved problem because build systems keep breaking in random places. Granted, these problems are in general easy to solve. But we're talking about death from a thousand papercuts here. In other words, boredom from a thousand compile errors.

stackskipton 2y ago
:shrug: Thousand compile errors sounds like Dev Team hasn't buckled down and fixed their build script (Dockerfile). Maybe they should take some time and do that. Other beauty about containers is ability to build in environment Devs control and any changes to build servers shouldn't impact them.
- amelius 2y ago
  Perhaps you have never been in the situation where one package forces you into a particular version which in turn forces its dependencies to versions, etc., eventually pushing you into an impossible situation. Anyway, I wish I had a Dev Team like you have to solve these problems for me ...
  - nyrikki 2y ago
    If you aren't leveraging the namespace abstraction of containers, why use them at all? Noting that I am being frank and honest here, but you don't have a dev problem here, but most likely an organization level problem. Namespaces and interface contracts should be dramatically reducing dependency issues, not causing them to explode.