Binctr: Static, unprivileged, self-contained containers as executable binaries

Re:Binctr: Static, unprivileged, self-contained containers a... by icebraining on Sunday December 23, 2018 @11:16AM (#18746855)

I have to admit that I'm quite confused about this comment. Are you saying simply running a command under its own uid is enough to provide the same isolation that containers do, and that the latter were only created because people are not running Linux natively?

[ Parent | on HN ]

Re:Binctr: Static, unprivileged, self-contained containers a... by g82918 on Sunday December 23, 2018 @11:38AM (#18746968)

I think he is saying there are a lot of 80% solutions like user based isolation that could have been made more secure, but instead people invented a new solution that has its own problems, and that the fractured landscape of solutions we see now is due to the freedom of open source.

[ Parent | on HN ]

Re:Binctr: Static, unprivileged, self-contained containers a... by dsr_ on Sunday December 23, 2018 @01:16PM (#18747455)

Run application:

- under its own userid

- in its own namespace for mount, network, process-id, user-id, ipc, uts and control groups

and presto, you are running in a container.

[ Parent | on HN ]