33 ms·
Basically : the OS is itself a layered read-only "container", on top of which flatpak is the recommended way to install applications. I wish someone built an O
by antpls 7y ago
Basically : the OS is itself a layered read-only "container", on top of which flatpak is the recommended way to install applications.
I wish someone built an OS based on k8s as a service and application orchestrator. We wouldn't have to reinvent all the config files, the command line tools and we could reuse knowledge between cluster and single-machine administration. Plus k8s already voluntary abstracted the underlying technologies, so it should be simple to reuse it. We would use the same high-availability concepts than from the cloud, such as stateless service, horizontal scaling of services, etc. We could also reuse Istio and all the standards it is built-on to introspect the system. In other words, a microservice based OS.
- curt15 7y agoIn some ways the implementation resembles ChromeOS -- you can install Linux tools and applications in a container, while the base OS is immutable and atomically updated via filesystem diffs.
- wmf 7y agoCheck out k3os and OpenShift/OKD 4.
- gigatexal 7y agoNo way. I get paid to write YAML hell for k8s at work. I don’t want my desktop to have to work like that. Not all things need to be K8s
- mycall 7y agoHow fast would Steam games play?
- colechristensen 7y agoRancherOS is a bit like your wish.
- jacques_chester 7y agohttps://kind.sigs.k8s.io/ https://kind.sigs.k8s.io/
- mises 7y agoI think that idea isn't really viable until we have a serious microkernel contender. We'll see how hurd goes, but personally, I'd put more stock in fuscia. A microkernel with a massive comlamy behind it (which employs much of the best software engineers there are and fully intends to bring it to market) is a seriously cool thought. Maybe we'll see debian 11/fuscia some time (though arch will still be better).
- polotics 7y agoYou've basically described Qubes OS, with K8S a less OS-y choice than Xen.