So, this has always bugged me. How do you validate a Docker container? No one wants to pull a laced up container, so there has to be a way one can check. Of course, sticking to original docker containers from Docker Hub would be one method I suppose. Is there some kind of scan one can do? I do this on my Windows computer; scan before installing. Besides looking at code that I would have no idea what is going on, what protocols do you guys use?

  • aksdb@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 day ago

    Well, a big advantage of containers is, that you can isolate them pretty aggressively. So if you run a container that is supposed to serve content on a single HTTP port, expose only that port, mount no unnecessary volumes and run it on a network that blocks all outgoing traffic. Ideally the only thing left will be incoming traffic on the one port the service is supposed to serve.

    • usuarioimanol@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      14 hours ago

      Block outgoing traffic, do you mean blocking it at my router or at the level of where I have the container hosted?

      • aksdb@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 hours ago

        I talk fully about software. Add appropriate nftable rules to the container network and that’s it.