3 ms·

Thanks, this is good info. For NodeJS and Rails, I use nvm and rvm, so didn't have any problem with multiple environments. But yeah, I see your point that Docke

• e12e 13y ago
  Have a dependency on conflicting libc is a favourite problem that can be difficult to solve without some form of container (vm, chroot or something "in between" like lxc/jails). Another is dependency on different kernel (either major version on same os, or dependency on a different kernel, like freebsd), which docker (by design) doesn't solve. I don't use ruby much, but it doesn't strike me as very easy to work with/very reliable for production deployment. But that might be me. How well does it handle dependencies on conflicting modules with parts written in c? Perhaps the most important point is that (when it makes sense) a docker setup might allow easier horizontal scale-out, and or redundancy. All that said, keeping things simple is generally a good thing. But sometimes adding complexity in one area makes the overall system less complex.