News for hackers. Stuff that matters.
Re:Containers as Kernel Objects – Again by InTheArena on Sunday February 24, 2019 @02:52PM (#19240234)
This approach has been very successful to date. People forget but there was actually quite a number of different rival container implementations. LXc and let me contain that for you, for example. The lack of a single abstraction made it possible for there to be rival implementations that each evolved rapidly. Now that Docker has “won” it’s time to simplify by collapsing all of the abstractions down to a single set of interfaces.
Re:Containers as Kernel Objects – Again by ithkuil on Sunday February 24, 2019 @03:50PM (#19240545)
How different is the actual underlying container abstraction between all those competing container "end-user experiences"?
Re:Containers as Kernel Objects – Again by RantyDave on Sunday February 24, 2019 @09:02PM (#19242182)
For the most part, completely identical. They all work by squirting numbers into cgroups.

The exception that proves the rule are the container runtimes that launch the container in a VM.

Re:Containers as Kernel Objects – Again by barbecue_sauce on Sunday February 24, 2019 @05:05PM (#19240909)
Isn't this essentially already happening with CRI-O and the OCI?