3 ms·
>The monolithic kernel folks just haven't noticed it. I know may be by sheer number of users most people use them in the cloud or for development but some of u
by noobermin 4y ago
>The monolithic kernel folks just haven't noticed it.
I know may be by sheer number of users most people use them in the cloud or for development but some of us do actually use linux on our everyday machines.
- pjmlp 4y agoWith docker?
- zamalek 4y ago> docker? > GP: development Probably yes? Even foregoing development scenarios, containers can be used for everyday Linux tasks with things like toolbox/distrobox (which do support GUIs).
- pjmlp 4y agoSo playing microkernels anyway, with worse performance due to the extra monolithic layers.
- remexre 4y agoHow are namespaces similar to microkernels? I see them a lot more as glorified chroot; it's not like there's a modprobe namespace or anything.
- pjmlp 4y agoNamespaces are a tiny part of what means a complete container infrastructure, across all OS layers. Then there is the whole IPC taking place across containers with much slower APIs and heavier context switch states.
- zamalek 4y agoContainers on Linux don't have slower APIs or IPC, and don't have heavier context switches. Are you sure you're not thinking about VMs?
- pjmlp 4y agoHow do containers communicate with each other?
- zamalek 4y agoSockets, shared memory, or the network, just like any Linux process.
- pjmlp 4y agoShared memory across containers, across isolation layers, that is a good one. The two remaining ones are worse than any micro-kernel API call in performace.
- zamalek 4y agoIt's explicit, just like all the other mapping/mounting options[1], and containers aren't exclusively for secure isolation anyway. Many examples exist where security isn't desirable, such as the afformentioned toolbox/distrobox. [1]: https://docs.docker.com/engine/reference/run/#ipc-settings---ipc https://docs.docker.com/engine/reference/run/#ipc-settings--...