CR]# CB]mkdir -p /srv/chroot/sarge

The author has each chroot as a separate LVM logical volume (LV). Create and mount an LV here if required:

CR]# CB]lvcreate -L 4G -n sarge_chroot -Z y hda_vg

Add to /etc/fstab and mount (see next section for full fstab example). Finally, run debootstrap to create the chroot:

CR]# CB]debootstrap --variant=buildd /srv/chroot/sarge http://ftp.uk.debian.org/debian/

An example /etc/fstab:

lfCR s s s s s. /dev//hda_vg/sarge_chroot [rs] lfCR lfCR lfCR lfCR lfCR lfCR. /srv/chroot/sarge ext3 defaults 0 2 /dev/pts /srv/chroot/sarge/dev/pts none rw,bind 0 0 tmpfs /srv/chroot/sarge/dev/shm tmpfs defaults 0 0 proc /srv/chroot/sarge/proc proc defaults 0 0 lfCR s s s s s. /dev/hda_vg/home [rs] lfCR lfCR lfCR lfCR lfCR lfCR. /srv/chroot/sarge/home ext3 quota 0 0 /tmp /srv/chroot/sarge/tmp none rw,bind 0 0 /etc/passwd /srv/chroot/sarge/etc/passwd none ro,bind 0 0 /etc/shadow /srv/chroot/sarge/etc/shadow none ro,bind 0 0 /etc/group /srv/chroot/sarge/etc/group none ro,bind 0 0 lfCR s s s s s. /etc/resolv.conf [rs] lfCR lfCR s s s s. /srv/chroot/sarge/etc/resolv.conf [rs] lfCR lfCR lfCR lfCR lfCR lfCR. none ro,bind 0 0

If the bind mountpoints don't exist in the chroot, touch them:

CR]# CB]touch /srv/chroot/sarge/etc/resolv.conf

Next, mount them all.

Depending on your kernel version and security considerations, you may wish to do this part slightly differently. With a Linux kernel, at least version 2.6 is required for bind mounts, and devpts (CONFIG_UNIX98_PTYS) for /dev/pts. Other guides recommend copying the files, but this method keeps them up-to-date at no cost.

If using sbuild with schroot, passwd, shadow, group and resolv.conf can be updated automatically at the start of each build, so no action is required here. schroot can also automatically mount all of the extra filesystems, so all the other mounts may be omitted.

To disable networking, don't bind mount /etc/resolv.conf. This will prevent APT from working inside the chroot, but prevents package building from having working network access (no nameservers).

Create or edit /srv/chroot/sarge/etc/apt/sources.list, and add all the APT sources required to obtain binary and source packages for your chosen distribution:

CR]deb http://security.debian.org/ sarge/updates main

CR]deb-src http://security.debian.org/ sarge/updates main

CR]

CR]deb http://ftp.uk.debian.org/debian/ sarge main

CR]deb-src http://ftp.uk.debian.org/debian/ sarge main

This is entirely optional, but will make the chroot environment easier to access and administer.

For dchroot, add the following line to /etc/dchroot.conf:

CR]sarge /srv/chroot/sarge

For schroot, add the a group to /etc/schroot/schroot.conf, for example:

CR][sarge]

CR]type=plain

CR]description=Debian sarge (stable)

CR]location=/srv/chroot/sarge

CR]priority=2

CR]groups=root,sbuild

CR]root-groups=sbuild

CR]aliases=stable

CR]run-setup-scripts=true

CR]run-session-scripts=true

CR]# CB]dchroot -c sarge

or

CR]$ CB]schroot -c sarge -u root

While running as root inside the chroot:

CR]# CB]apt-get update

CR]# CB]apt-get dist-upgrade

CR]# CB]apt-get install debconf

CR]# CB]dpkg-reconfigure -plow debconf

Answer the debconf questions as follows:

interface

choose 6/Noninteractive

priority

choose 1/Critical

You only need to run dpkg-reconfigure if you weren't asked the questions during the debconf install. Next, install the packages required for building packages:

CR]# CB]apt-get install sudo debfoster fakeroot build-essential

CR]# CB]apt-get install makedev

CR]# CB]cd /dev/

CR]# CB]/sbin/MAKEDEV generic

CR]# CB]touch /etc/mtab

For some security, we don't bind mount /dev, so it can't access e.g. USB devices

While running as root inside the chroot:

CR]# CB]mkdir /build

CR]# CB]chown root:sbuild /build

CR]# CB]mkdir -p /var/lib/sbuild/srcdep-lock

CR]# CB]chown -R root:sbuild /var/lib/sbuild

CR]# CB]chmod -R 02775 /var/lib/sbuild

Note that when using sbuild with schroot, this setup is done at the start of each build, so is not required here.

Congratulations! You should now have a fully configured and operational chroot.

Configure the user's ~.sbuildrc:

CR]$ CB]cp /usr/share/doc/sbuild/examples/example.sbuildrc ~/.sbuildrc

Edit to set the correct mail address to send log files to, and the correct maintainer name and/or uploader name.

Create the required build directories (The .sbuildrc may have configured different locations; these are the defaults):

CR]$ CB]mkdir ~/build ~/logs

As root, run:

CR]# CB]/usr/share/sbuild/add_sbuild_user /srv/chroot/sarge stable <username>

Follow the instructions displayed, and update ~/build etc. as shown.

If using sbuild with sudo (chroot_mode [lq]split[rq]), sudo needs configuring to give the user permission to install and remove packages in the chroot, which requires root priveleges. Add the following lines to /etc/sudoers

CR]CI]username ALL=NOPASSWD: ALL

CR]Defaults:CI]username env_keep+="APT_CONFIG DEBIAN_FRONTEND"

where username is the name of the user who will run sbuild. /etc/sudoers inside the chroot also needs the same modifications.

You should now be able to run sbuild.

CR]$ CB]cd ~/build

CR]$ CB]sbuild ...