Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
depends on your job role but for my job we have 1 project that's not containerized and each time we have issues with it I want to crush my fucking balls
containerization is incredibly wasteful but it does solve some problems
How is it wasteful?
like flatpak. when you don't build all your containers on the same base image and shared layers, then you'll store lots of slightly different versions of the same libraries and other files, both on disk, and then in memory
I see. I was more thinking in terms of CPU/RAM resources where it's far cheaper to just run a single process instead of a VM for it, etc.
but containerization does not use VMs. containers share the same kernel, but userspace and resources are separated with namespaces. it has a very little overhead
Yes that being my point. When you said wasteful I was thinking you were criticizing them vs VMS which makes no sense.
Even the duplication of layers makes little sense as one, storage is cheap and two, even duplicated they far more than make up for it without needing VMS per.
But then I also see you aren't op who I originally directed the question to.