Submitted 10 months ago by irmadlad@lemmy.world to selfhosted@lemmy.world
https://lemmy.world/pictrs/image/9f25256d-9b87-4846-bdbf-270552bf19a1.jpeg
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?
Bot? What’s with the image?
I would guess real person. Posts without images just get very little traffic, so I assume thats why people are starting to post this.
Oh god the lemmings are optimizing posts for engagement. We are approaching peak content
Are you looking for docs.docker.com/build/metadata/attestations/?
I didn’t know that existed. I’m reading presently.
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?
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.
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.
aksdb@lemmy.world 10 months 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 10 months 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 10 months ago
I talk fully about software. Add appropriate nftable rules to the container network and that’s it.