On Mon, Dec 28, 2015 at 4:29 PM, Emmanuel Coirier wrote:
>
> I'll look at multistrap. It let you customize device creation. It should then
> be possible to customize it to not create any device...
>
Multistrap doesn't do 'device node' creation at all. It uses APT to
download packages to a direct
> Johan Ouwerkerk [mailto:jm.ouwerk...@gmail.com]
> Maybe try --variant=fakechroot ?
Already tested : it still create those devices. The debootstrap script doesn't
have any option to disable devices creation or ignore errors produced by this
operation.
I've tried with appending "|| tue" to the
Thanks for your answer, but...
> Mantas Mikulėnas [mailto:somewhere]
> Hmm, isn't debootstrap supposed to run outside the container? Or are you
> trying to nest two containers?
It's indeed a nested container. The outer container is a working container in
which I do all I need to do. The inner c
On Thu, Dec 24, 2015 at 12:45 AM, Lennart Poettering
wrote:
>
> Why does debootstrap create device nodes at all? Does Debian support
> setups with /dev being on persistent media? Note that udev has not
> supported non-devtmpfs boots since a long time. If Debian requires
> udev, then there's really
On Wed, 23.12.15 23:12, Johan Ouwerkerk (jm.ouwerk...@gmail.com) wrote:
> > My goal is to have a light container able to build a software that runs in
> > a light container (actually in a legacy chroot). And one of the first steps
> > is to debootstrap a virgin system. Is this use case possible
> My goal is to have a light container able to build a software that runs in a
> light container (actually in a legacy chroot). And one of the first steps is
> to debootstrap a virgin system. Is this use case possible ?
Maybe try --variant=fakechroot ? Haven't tested this but my guess is
that if
On Wed, 23.12.15 14:10, Emmanuel Coirier (ecoir...@olfeo.com) wrote:
> Hello everyone,
>
> I have encountered a problem with a systemd-nspawn container and deboostrap
> running in this container.
>
> When I try to launch deboostrap inside the container, debootstrap
> stops because it tries to u
On Wed, Dec 23, 2015 at 3:10 PM, Emmanuel Coirier
wrote:
> Hello everyone,
>
> I have encountered a problem with a systemd-nspawn container and
> deboostrap running in this container.
>
> When I try to launch deboostrap inside the container, debootstrap stops
> because it tries to unpack a tar ar
Hello everyone,
I have encountered a problem with a systemd-nspawn container and deboostrap
running in this container.
When I try to launch deboostrap inside the container, debootstrap stops because
it tries to unpack a tar archive that creates devices like /dev/console. The
error is "EPERM".
