From: Gilles (gilles_at_harfang.homelinux.org)
Date: Mon 12 Sep 2005 - 00:59:47 BST
> > I tried to build a vserver with the "debootstrap" method (using
> > the "--arch" and "--foreign" options), but didn't succeed: the
> > "--second-stage" aborts with
> Try building the image with plain debootstrap, ie without vserver xxx
> build -m debootstrap.
> If that doesn't work, it's probably not specifically vserver-related.
That's right. It was only a missing dependency.
Nevertheless, I have new problems with "debootstrap".
I used the "--exclude" option in order to not install hardware-related
packages (and some others):
But, it seems that, contrary to the manpage warning, "debootstrap"
installs some of them anyway, namely "modutils", "mount" and "makedev".
These are tagged as "required", but should not be in a vserver.
Is there a way to deal with this at the "debootstrap" level or is the
only solution to try and remove them afterwards from within the vserver?
Here attached are 2 files listing the contents of the "/dev" directory.
One is after the first stage of "debootstrap" (which seems fine), the
other after the completion of the second stage; the former contains
many devices which shouldn't be there in a vserver (strangely, a lot
of them audio-related).
Why does this happen and how can it be avoided?
Although this is more related to Debian than vserver, the main point is
to try and define the proper method to create a "clean" Debian vserver,
where by "clean" I mean:
* Not containing any packages which may attempt to perform actions
forbidden inside a vserver (i.e. hardware-related stuff).
* Containing only the strict minimum for the vserver to function as a
Debian distribution (i.e. with the ability to install and remove
Thanks for your suggestions.
Vserver mailing list