3 ms·

I think I'm missing something here. What is it that makes docker complicated or dangerous for deploying applications? I don't understand how the argument goes

• jaequery 8y ago
  Well it can be dangerous if the image maintainer were to put something malicious in the build, like log all requests and send it somewhere else. Although the same can be said for any package management libraries (npm, apt, etc), because Docker works at a server level, it opens up a whole new ballpark of exploitations on your app.
  • robbyt 8y ago
    Running untrustworthy code can be risky? Nothing new here. This is not Docker's fault. Anyone can download and run untrusted code, even without Docker.
    • jaequery 8y ago
      Yea, and that was exactly my point
• KaiserPro 8y ago
  Because it actively promoted "it works on my machine" and "snowflake" installs. Supporting a legacy docker app (ie something that was shipped two years ago) is a massive nightmare, because the build system used to make it is almost certainly not going to work. This means keeping the software patched becomes a massive massive pain. (mind you the same argument can be said for statically compiled binaries) The assumptions, the wrapper, and the plain horror that is the storage system is just such an arse.