* Jeff Jansen schrieb: > When using debootstrap you can just add "-- -arch i386" to the end of > your command. > > # vserver lenny32 build -m debootstrap --context 72 \ > --hostname lenny32 --interface lenny32=eth0:192.168.128.72/24 \ > -- -d lenny -- -arch i386 # vserver lenny32 build --force -m debootstrap --context 72 --hostname lenny32 \ --interface lenny32=eth0:192.168.128.72/24 -- -d lenny -- -arch i386 chroot-sh: open("/etc/apt/sources.list"): No such file or directory >>> Executing post install script ... secure-mount: chdir("/tmp"): No such file or directory /etc/vservers/lenny32/fstab:2:1: failed to mount fstab-entry vcontext: execvp("bash"): No such file or directory wait(): No child processes An error occured while executing the vserver startup sequence; when there are no other messages, it is very likely that the init-script (bash -c exec > /dev/null exec 2> /dev/null trap 'kill -s 9 -- -1; exit 0' INT sleep 30 kill -s 15 -- -1 sleep 1 kill -s 9 -- -1) failed. Common causes are: * /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build method knows how to deal with this, but on existing installations, appending 'true' to this file will help. Failed to start vserver 'lenny32' 'vserver ... suexec' is supported for running vservers only; aborting... 'vserver ... suexec' is supported for running vservers only; aborting... 'vserver ... suexec' is supported for running vservers only; aborting... BTW: a directory i386 is created in /var/lib/verservers/ ! Creation the vserver configuration without i386 works: ====================================================== # vserver lenny32 build -m debootstrap --context 72 --hostname lenny32 --interface \ lenny32=eth0:192.168.128.72/24 -- -d lenny I: Retrieving Release I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... [...] test32=eth0:192.168.128.72/24 -- E: No such script: /usr/share/debootstrap/scripts/deb5.0.5 Perhaps a syntax fault? tia Ekkard