[9front] Containers

[9front] Containers

[Jubal Biggs]

[-- Attachment #1: Type: text/plain, Size: 294 bytes --]

Hey, general question; has anyone been able to set up a containerized
service (Docker or otherwise) on Plan9? I guess it requires the Linux
kernel, which would not be optimal to run on top of a Plan9 environment,
but that sort of virtualization would open up a whole universe of
possibilities.

[-- Attachment #2: Type: text/html, Size: 319 bytes --]

Re: [9front] Containers

[Kurt H Maier]

On Mon, Nov 29, 2021 at 10:38:58PM -0500, Jubal Biggs wrote:
> Hey, general question; has anyone been able to set up a containerized
> service (Docker or otherwise) on Plan9? I guess it requires the Linux
> kernel, which would not be optimal to run on top of a Plan9 environment,
> but that sort of virtualization would open up a whole universe of
> possibilities.

Plan 9 doesn't need containerization; we have user-controllable
namespaces, which is the feature that Linux container tools poorly
imitate.  We do have some virtualization software, if you want to
artificially cripple your environment and then inadequately reconstruct
the features you left behind by booting a Linux kernel.

khm

Re: [9front] Containers

[Lucas Francesco]

The best container that can exist is called a process with its own
namespace and place to write/exist. If you really any form/gimmick of
"contenarization" (the linux-grade thing, with a snapshot of the whole
container and importing/exporting between machines thing)  I think you
should checkout how plan9ants was setup on top of 9front (but with
venti-backed fossil rootscores ) to give on-demand isolated cpu
servers with its own root on a specific namespace (it was all on the
same kernel, not virtualized, but different /root and enviroment for
each user)

On Tue, 30 Nov 2021 at 04:27, Kurt H Maier <khm@sciops.net> wrote:
>
> On Mon, Nov 29, 2021 at 10:38:58PM -0500, Jubal Biggs wrote:
> > Hey, general question; has anyone been able to set up a containerized
> > service (Docker or otherwise) on Plan9? I guess it requires the Linux
> > kernel, which would not be optimal to run on top of a Plan9 environment,
> > but that sort of virtualization would open up a whole universe of
> > possibilities.
>
> Plan 9 doesn't need containerization; we have user-controllable
> namespaces, which is the feature that Linux container tools poorly
> imitate.  We do have some virtualization software, if you want to
> artificially cripple your environment and then inadequately reconstruct
> the features you left behind by booting a Linux kernel.
>
> khm

Re: [9front] Containers

[Lucas Francesco]

oops, i meant spawngrid, not plan9ants.

On Tue, 30 Nov 2021 at 11:28, Lucas Francesco
<lucas.francesco93@gmail.com> wrote:
>
> The best container that can exist is called a process with its own
> namespace and place to write/exist. If you really any form/gimmick of
> "contenarization" (the linux-grade thing, with a snapshot of the whole
> container and importing/exporting between machines thing)  I think you
> should checkout how plan9ants was setup on top of 9front (but with
> venti-backed fossil rootscores ) to give on-demand isolated cpu
> servers with its own root on a specific namespace (it was all on the
> same kernel, not virtualized, but different /root and enviroment for
> each user)
>
> On Tue, 30 Nov 2021 at 04:27, Kurt H Maier <khm@sciops.net> wrote:
> >
> > On Mon, Nov 29, 2021 at 10:38:58PM -0500, Jubal Biggs wrote:
> > > Hey, general question; has anyone been able to set up a containerized
> > > service (Docker or otherwise) on Plan9? I guess it requires the Linux
> > > kernel, which would not be optimal to run on top of a Plan9 environment,
> > > but that sort of virtualization would open up a whole universe of
> > > possibilities.
> >
> > Plan 9 doesn't need containerization; we have user-controllable
> > namespaces, which is the feature that Linux container tools poorly
> > imitate.  We do have some virtualization software, if you want to
> > artificially cripple your environment and then inadequately reconstruct
> > the features you left behind by booting a Linux kernel.
> >
> > khm