this post was submitted on 02 Nov 2023
54 points (95.0% liked)

Selfhosted

60526 readers
1293 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] azdle@news.idlestate.org 16 points 2 years ago* (last edited 2 years ago) (1 children)

Defense in depth. If something escapes the container it's limited to only what's under that user and not the whole system. Having access to the whole system makes it easier for malware to hide/persist itself.

[–] lemmyvore@feddit.nl -4 points 2 years ago (2 children)

Correct me if I'm wrong but containerization is enforced by the kernel, correct? If something escapes you're pretty much screwed anyway.

[–] Atemu@lemmy.ml 13 points 2 years ago

There are many layers involved in preventing escapes from containers.

[–] Sethayy@sh.itjust.works 2 points 2 years ago

Way too dependent on the setup, a container with absolutely no outside access theoretically just has the kernel, but usually we want to communicate with our docker images not just run them