4 ms·
Saying Google didn’t have to reinvent containers when Google invented containers is .. something (https://en.wikipedia.org/wiki/Cgroups https://en.wikipedia.org
by rrdharan 2y ago
Saying Google didn’t have to reinvent containers when Google invented containers is .. something (https://en.wikipedia.org/wiki/Cgroups https://en.wikipedia.org/wiki/Cgroups).
- kccqzy 2y agoIt's somewhat unusual for Google to open source and mainline this bit of functionality. Last time I heard, Google's internal production Linux kernel still has 9000+ patches[0] on top of vanilla Linux. And I'm still waiting for them to open source switchto[1]. [0]: https://lwn.net/Articles/871195/ https://lwn.net/Articles/871195/ [1]: https://www.youtube.com/watch?v=KXuZi9aeGTw https://www.youtube.com/watch?v=KXuZi9aeGTw
- rrdharan 2y agoThey tried, it died: https://lkml.org/lkml/2020/7/22/1204 https://lkml.org/lkml/2020/7/22/1204
- jauntywundrkind 2y agoAnd for a brief couple years Google had an offering the world could use that exposed that invention. Via the stock, well respected LXC tool. They created something, only to never ever use it in public eye. To go keep reinventing and keep NIH'ing. The android virtualization stack is fucking wild, and hardly used, offers such a meager fraction of what ChromeOS was doing. Not a bad callout, but this seems like a particularly glorious & vicious slam... that doesn't change the big picture on iota.
- surajrmal 2y agoAndroid is reusing the ChromeOS vmm, crosvm. How is it less capable?
- pjmlp 2y agoThey invented containers on Linux kernel. Containers on UNIX and mainframes predate Google's existence.
- pxeger1 2y agocgroups are neither necessary nor sufficient for Linux containers
- yencabulator 2y agoCgroups is a kernel feature, parent is talking about the userspace stack for managing containers. Google uses LXC in crosvm, and didn't have to program it from scratch.