|
|
Subscribe / Log in / New account

Poettering: Revisiting how we put together Linux systems

Poettering: Revisiting how we put together Linux systems

Posted Sep 1, 2014 16:46 UTC (Mon) by raven667 (subscriber, #5198)
In reply to: Poettering: Revisiting how we put together Linux systems by torquay
Parent article: Poettering: Revisiting how we put together Linux systems

> Perhaps there's an easier way to skin the cat: have each app run inside its own Docker container, but with access to a common /home partition. All the libraries and runtime required for the app are bundled with the app, including an X or Wayland display server (*). The windows produced by the app are captured and shown by a "master" display server. It's certainly a heavy handed and size-inefficient solution, but this is the price to pay to tame the constant API and ABI brokenness.

Sure, one of the reasons Docker exists and is so popular is to try and skin this cat, heck the reason VMs are so popular is to abstract away this software dependency management problem in a simple but heavy handed way. The problem is that no one really wants to run nested kernels to make this work, you lose a lot of information about the work to be scheduled when nesting kernels, so this is a possible way to solve the fundamental software compatibility management problem on a shared kernel.

I'm sure that as others digest this proposal and try to build systems using it they will discover corner cases which are not handled, compatibility issues, ways to simplify it so that the final result may be somewhat different but this could be a vastly useful system.


to post comments


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds