116

The question above for the most part, been reading up on it. Also want to it for learning purposes.

you are viewing a single comment's thread
view the rest of the comments
[-] BaldProphet@kbin.social 2 points 1 year ago

I mean, if you have around 17 million containers running services, maybe.

[-] dpflug@hachyderm.io 1 points 1 year ago* (last edited 1 year ago)

@BaldProphet
What's the smallest container around? How much RAM would that take?

edit: FROM scratch let's you run bare binaries on Docker.

Would be very interesting to see how far that could get. What sort of payload/task would be interesting for all those containers?
@Sandbag @bdonvr

[-] gedhrel@lemmy.ml 1 points 1 year ago

Doesn't need to be a "traditional" container. Modulo noisy-neighbour issues, wasm sandboxing could potentially offer an order of magnitude better density (depending on what you're running; this might be more suited to specific tasks than providing a substrate for a general-purpose conpute service).

[-] dpflug@hachyderm.io 0 points 1 year ago

@gedhrel
wasm sandboxes can take IPs? Regardless, if we're just talking density, I can put multiple IPs on a single interface or create a ton of virtual interfaces. That's boring, though.

[-] gedhrel@lemmy.ml 1 points 1 year ago

Yes. The sandbox gets whatever capabilities you expose to it.

[-] BaldProphet@kbin.social 1 points 1 year ago

It's definitely an interesting hypothetical. Some homelabs that I've seen run crazy enterprise gear and are certainly capable of running thousands of very small containers, while others are running repurposed consumer equipment or SBCs like Raspberry Pis with less computing power and RAM.

Of course, in a self-hosted or homelab environment, there would be little utility to running that many network or web services. It would be a neat experiment, though. Seems like the kind of thing that Linus Tech Tips would attempt.

this post was submitted on 13 Jul 2023
116 points (95.3% liked)

Selfhosted

40406 readers
314 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