• @federico3
    link
    23 years ago

    docker is really bad for security and adds a lot of unnecessary complexity

    • @remram
      link
      0
      edit-2
      3 years ago

      Docker is not bad for security, unless you do insecure things like exposing your Docker socket or running random workloads as root, however those are just as insecure under systemd.

      • @nutomicOPMA
        link
        53 years ago

        It has some weird behaviour, for example ufw rules dont apply to Docker.

        • @remram
          link
          -13 years ago

          This is not insecure. It is surprising if you don’t know how containers work, but in a real deployment you’d only bind to localhost and use a reverse proxy and that is perfectly safe.

          • @ajz
            link
            1
            edit-2
            2 years ago

            deleted by creator

            • @remram
              link
              13 years ago

              As I said this is surprising if you don’t know how containers work. This is similar from how e.g. virtual machine networking would trip you. As long as you know how to set things up properly, which is documented at length, Docker is not “insecure”.

              • @ajz
                link
                1
                edit-2
                2 years ago

                deleted by creator

                • @remram
                  link
                  1
                  edit-2
                  3 years ago

                  So-called “bridged networking” is not the default for VirtualBox but it is recommended for Qemu, yes. In that case only the routing rules on the bridge apply, not the filtering rules on your host’s interface.

        • @remram
          link
          1
          edit-2
          3 years ago

          How is this different from say, SystemD? It runs as root and has a larger attack surface.

          The link you pointed out has every CVE for every application packaged as Docker image. Would you make the same point that APT or AppImage is insecure because there are insecure applications packaged that way?

          • @federico3
            link
            23 years ago

            How is this different from say, SystemD?

            It’s very different because SystemD does way more things than running containers. Also, this is whataboutism.

            The link you pointed out has every CVE for every application packaged as Docker image.

            You could scan through the list and check for yourself which ones are due to docker itself. Besides, I updated the link to filter out the spurious CVEs.

            Would you make the same point that APT or AppImage is insecure because there are insecure applications packaged that way?

            I would not… unless the tool itself was actively encouraging bad security practices, for example bundling dependencies, as Docker/AppImage/Flatpak/Snap do.

            • @remram
              link
              03 years ago

              It is not whataboutism since SystemD is what you’ll use to run services if you don’t use Docker… If I say that mass transit is a terrible idea because it pollutes, and you point out that cars pollute even more, I can’t claim “whataboutism” to dismiss your argument.

              Here’s the corresponding page for SystemD: https://www.cvedetails.com/product/38088/Freedesktop-Systemd.html?vendor_id=7971 as you can see there are even more vulnerabilities, which makes sense as the attack surface is even larger.