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?

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 month ago

    This isn’t a clear question about what you’re trying to confirm here.

    Are you wondering how you pull a confirmed container from a confirmed provider?

    Are you concerned about supply chain attacks?

    • irmadlad@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      I do know how to pull containers. I’m concerned with pulling a Docker container, that may be laced with xmrig for example, or opens a port by which a nefarious actor could gain access, much like in a windows environment. There are repositories like Docker Hub, but do they go through and verify all containers? I highly doubt they verify user content/containers. They do have verified containers, but not all of them bear the verified earmark.

      • just_another_person@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        30 days ago

        Don’t pull containers from random sources then. If you’re working with a specific project, only pull from their official images.

        Pushed images are built and verified from the maintainers, then pushed. Then you pull, each layer is verified by hash that it is the same image as was originally pushed by the maintainers.

        Whether that project protects itself from supply chain attacks is a different story, but as far as ports go, you only expose what you tell it to expose. There’s no workaround for that.