MIME-Version: 1.0
References: <B623F07E-FD90-4D6B-B7A7-0B796019CF2C@extremeshok.com>
In-Reply-To: <B623F07E-FD90-4D6B-B7A7-0B796019CF2C@extremeshok.com>
From: Parke <parke.nexus@gmail.com>
Date: Sun, 28 Jun 2020 15:02:01 -0700
Message-ID: <CAPxz1+YSaMQm4LWjn8mChpFbUfeDKFdaUrL1UrkqTTqEdj7LfQ@mail.gmail.com>
Subject: Re: Running Alpine's userland in a Linux user namespace via lxroot
To: "admin@extremeshok.com" <admin@extremeshok.com>
Cc: ~alpine/users@lists.alpinelinux.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Jun 28, 2020 at 1:22 PM admin@extremeshok.com
<admin@extremeshok.com> wrote:
> Very interesting project.

Thanks.

> What=E2=80=99s the benefit over using docker ? Don=E2=80=99t need root ac=
cess ?

Correct, root access not required.  But also:

(Much?) smaller(?) codebase.  Probably also much smaller executable
size:  A debug build of lxroot is 355KB.  Compiled without debugging
info, lxroot is 132KB.

More transparency?  (lxroot makes it easy to know where all the files
are.  lxroot makes it easy to know which user IDs will be used.)

Easy to "share" files (by bind mounting directories) between the host
and lxroot environments.  Or between two lxroot environments.

Conceptually simpler?  Fewer moving pieces make lxroot easier to understand=
?

The above are mostly guesses, as I have never used Docker.  I have
tried to use LXC and LXD, but I was never satisfied with the results.