9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Lucas Francesco <lucas.francesco93@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Containers
Date: Tue, 30 Nov 2021 11:28:31 -0300	[thread overview]
Message-ID: <CAF=5iUXOXxYr5w5+jxjZ2hwF6b2fumXb2MXfnsBQC-a0Ndg8Ow@mail.gmail.com> (raw)
In-Reply-To: <YaW7ODNwu5FWEO1r@wopr>

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

  reply	other threads:[~2021-11-30 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30  3:38 Jubal Biggs
2021-11-30  5:48 ` Kurt H Maier
2021-11-30 14:28   ` Lucas Francesco [this message]
2021-11-30 14:29     ` Lucas Francesco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAF=5iUXOXxYr5w5+jxjZ2hwF6b2fumXb2MXfnsBQC-a0Ndg8Ow@mail.gmail.com' \
    --to=lucas.francesco93@gmail.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).