this post was submitted on 20 May 2025
12 points (62.5% liked)

Selfhosted

46672 readers
426 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 4 points 1 week ago (6 children)

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.world 1 points 1 week ago (5 children)

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.

[–] tko@tkohhh.social 7 points 1 week ago* (last edited 1 week ago) (1 children)

I'm far from an expert, but it seems to me that if you're setting up your containers according to best practice you would only be mapping the specific ports needed for the service, which renders a wayward "open port" useless. If there's some kind of UI exploit, that's a different story. Perhaps this is why most people suggest not exposing your containerized services to the WAN. If we're talking about a virus that might affect files, it can only see the files that are mapped to the container which limits the damage that can be done. If you are exposing sensitive files to your container, it might be worth it to vet the container more thoroughly (and make sure you have good backups).

[–] rumba@lemmy.zip 2 points 1 week ago (1 children)

I suspect somebody could do some damage if they managed to infiltrate one of the reverse proxy containers. That might net you some useful credentials from the home gamers as they're doing the HTTPS wrapping themselves.

Any container that gets accessed with a web browser could potentially contain zero day exploits, But truth zero days with a maximum CVE value are rare.

[–] usuarioimanol@lemmy.world 1 points 1 week ago (1 children)

I have ports controlled but I use containers with http, however it is not exposed to the WAN, only to the LAN, is it equally risky?

[–] rumba@lemmy.zip 2 points 1 week ago

If you're not open to the wan, you're in decent enough shape.

The bar in your situation is that someone would need to shove a ransomware payload into a JavaScript 0-day for a package in your container without anyone noticing it, you'd have to update your container with it, then visit it with a vulnerable internet-connected computer. It's not impossible, but a really long, long shot.

load more comments (3 replies)
load more comments (3 replies)