个人工具

“UbuntuHelp:DebootstrapChroot”的版本间的差异

来自Ubuntu中文

跳转至： 导航, 搜索
小 （新页面: {{From|https://help.ubuntu.com/community/DebootstrapChroot}} {{Languages|UbuntuHelp:DebootstrapChroot}} == DebootstrapChroot == This article shows you how to use [http://packages.ubuntu....）
 
小
第2行： 第2行：
 
{{Languages|UbuntuHelp:DebootstrapChroot}}
 
{{Languages|UbuntuHelp:DebootstrapChroot}}
 
== DebootstrapChroot ==
 
== DebootstrapChroot ==
−
 
 
This article shows you how to use [http://packages.ubuntu.com/debootstrap debootstrap] to build a ''chroot environment'' that you can use for various needs, from trying out the latest (or even oldest ;) Ubuntu releases, or even working with [http://www.debian.org Debian] releases, to utilizing the chroot as a package building environment.
 
This article shows you how to use [http://packages.ubuntu.com/debootstrap debootstrap] to build a ''chroot environment'' that you can use for various needs, from trying out the latest (or even oldest ;) Ubuntu releases, or even working with [http://www.debian.org Debian] releases, to utilizing the chroot as a package building environment.
−
 
 
You can work anywhere - this Howto will assume you're using <code><nowiki>/var/chroot</nowiki></code> .  It will also assume that you want to install a BreezyBadger chroot; if you are going to use other Ubuntu releases, replace ''breezy'' below with ''warty'' for WartyWarthog, ''hoary'' for HoaryHedgehog, ''dapper'' for DapperDrake, ''edgy'' for EdgyEft, or "feisty" for FeistyFawn.
 
You can work anywhere - this Howto will assume you're using <code><nowiki>/var/chroot</nowiki></code> .  It will also assume that you want to install a BreezyBadger chroot; if you are going to use other Ubuntu releases, replace ''breezy'' below with ''warty'' for WartyWarthog, ''hoary'' for HoaryHedgehog, ''dapper'' for DapperDrake, ''edgy'' for EdgyEft, or "feisty" for FeistyFawn.
−
 
 
=== Getting and installing debootstrap ===
 
=== Getting and installing debootstrap ===
−
 
 
For the least pain and gnashing of teeth, please get the Ubuntu binary packages ''manually'':
 
For the least pain and gnashing of teeth, please get the Ubuntu binary packages ''manually'':
−
 
 
* http://packages.ubuntu.com/hoary/admin/debootstrap - If you want a ''hoary'' chroot
 
* http://packages.ubuntu.com/hoary/admin/debootstrap - If you want a ''hoary'' chroot
 
* http://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.1.4ubuntu4_all.deb - If you want a ''breezy'' chroot
 
* http://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.1.4ubuntu4_all.deb - If you want a ''breezy'' chroot
第17行： 第12行：
 
* http://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb - If you want a ''feisty'' chroot (if that's not available go to http://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/ and find the newest one)
 
* http://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb - If you want a ''feisty'' chroot (if that's not available go to http://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/ and find the newest one)
 
Example: Terminal session <code><nowiki>wget</nowiki></code>-ing and installing the latest Feisty debootstrap:
 
Example: Terminal session <code><nowiki>wget</nowiki></code>-ing and installing the latest Feisty debootstrap:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
wget http://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb
 
wget http://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb
 
sudo dpkg --install debootstrap_0.3.3.2ubuntu3_all.deb
 
sudo dpkg --install debootstrap_0.3.3.2ubuntu3_all.deb
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
=== Installing and configuring dchroot ===
 
=== Installing and configuring dchroot ===
−
 
 
[http://packages.ubuntu.com/dchroot dchroot] is a convenient means of managing chroot environments; with this tool you can have both Breezy, Dapper, and even Debian Sid chroots in your Ubuntu install, and using a chroot environment is a simple as <code><nowiki>dchroot -c dapper -d</nowiki></code> ;)
 
[http://packages.ubuntu.com/dchroot dchroot] is a convenient means of managing chroot environments; with this tool you can have both Breezy, Dapper, and even Debian Sid chroots in your Ubuntu install, and using a chroot environment is a simple as <code><nowiki>dchroot -c dapper -d</nowiki></code> ;)
−
 
 
To get it <code><nowiki>dchroot</nowiki></code> working in your system, just do the following in a Terminal:
 
To get it <code><nowiki>dchroot</nowiki></code> working in your system, just do the following in a Terminal:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo apt-get install dchroot
 
sudo apt-get install dchroot
第34行： 第24行：
 
sudo editor /etc/dchroot.conf
 
sudo editor /etc/dchroot.conf
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
Then append this line in <code><nowiki>/etc/dchroot.conf</nowiki></code>:
 
Then append this line in <code><nowiki>/etc/dchroot.conf</nowiki></code>:
 
<pre><nowiki>
 
<pre><nowiki>
 
mychroot /var/chroot
 
mychroot /var/chroot
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
=== Setting up your chroot with debootstrap ===
 
=== Setting up your chroot with debootstrap ===
−
 
 
If you want a 32-bit chroot on amd64 add <code><nowiki>--arch i386</nowiki></code> to this command line.  If you use the chroot to build packages add <code><nowiki>--variant=buildd</nowiki></code> .  Change ''breezy'' to according to your needs to ''warty'', ''hoary'', or ''dapper'', or leave as is for ''breezy'' chroot.
 
If you want a 32-bit chroot on amd64 add <code><nowiki>--arch i386</nowiki></code> to this command line.  If you use the chroot to build packages add <code><nowiki>--variant=buildd</nowiki></code> .  Change ''breezy'' to according to your needs to ''warty'', ''hoary'', or ''dapper'', or leave as is for ''breezy'' chroot.
−
 
 
To actually install the base chroot, open a Terminal and do:
 
To actually install the base chroot, open a Terminal and do:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo debootstrap --variant=buildd --arch i386 breezy /var/chroot/ http://archive.ubuntu.com/ubuntu/
 
sudo debootstrap --variant=buildd --arch i386 breezy /var/chroot/ http://archive.ubuntu.com/ubuntu/
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
<code><nowiki>debootstrap</nowiki></code> will then build a BreezyBadger chroot in <code><nowiki>/var/chroot/</nowiki></code>, getting the base packages in <code><nowiki>http://archive.ubuntu.com/ubuntu/</nowiki></code>, and, depending on the given additional options (in square brackets,) <code><nowiki>debootstrap</nowiki></code> will build a chroot for the given architecture and variant.
 
<code><nowiki>debootstrap</nowiki></code> will then build a BreezyBadger chroot in <code><nowiki>/var/chroot/</nowiki></code>, getting the base packages in <code><nowiki>http://archive.ubuntu.com/ubuntu/</nowiki></code>, and, depending on the given additional options (in square brackets,) <code><nowiki>debootstrap</nowiki></code> will build a chroot for the given architecture and variant.
−
 
 
If <code><nowiki>debootstrap</nowiki></code> finishes successfully, you'll be left with a base chroot in <code><nowiki>/var/chroot</nowiki></code>, which is, well, hardly suitable for anything very interesting.  To actually get our chroot to work and be able to, say, grab packages from the network, do the following right after <code><nowiki>debootstrap</nowiki></code>:
 
If <code><nowiki>debootstrap</nowiki></code> finishes successfully, you'll be left with a base chroot in <code><nowiki>/var/chroot</nowiki></code>, which is, well, hardly suitable for anything very interesting.  To actually get our chroot to work and be able to, say, grab packages from the network, do the following right after <code><nowiki>debootstrap</nowiki></code>:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo cp /etc/resolv.conf /var/chroot/etc/resolv.conf
 
sudo cp /etc/resolv.conf /var/chroot/etc/resolv.conf
第68行： 第50行：
 
exit
 
exit
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
You can stop here if you want and have a simple chroot that you use as root (<code><nowiki>sudo chroot /var/chroot</nowiki></code>).  If you want to use your chroot as another user and have access to your normal /home etc inside the chroot, carry on ;)
 
You can stop here if you want and have a simple chroot that you use as root (<code><nowiki>sudo chroot /var/chroot</nowiki></code>).  If you want to use your chroot as another user and have access to your normal /home etc inside the chroot, carry on ;)
−
 
 
If you want to build a Debian chroot on an Ubuntu system you need to point it at a Debian archive:
 
If you want to build a Debian chroot on an Ubuntu system you need to point it at a Debian archive:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo debootstrap --arch i386 sid sid/ http://ftp.uk.debian.org/debian/
 
sudo debootstrap --arch i386 sid sid/ http://ftp.uk.debian.org/debian/
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
=== Setting up a dchroot (non-root) environment ===
 
=== Setting up a dchroot (non-root) environment ===
−
 
 
<code><nowiki>dchroot</nowiki></code> makes it possible to use your newly-built chroot even as a non-root user.  Hence, you can configure your chroot environment in such a way that you can even use your existing <code><nowiki>/home</nowiki></code> as the chroot's <code><nowiki>/home</nowiki></code>, thereby saving you some expensive moving in between homes, as well as making package building/testing a ''LOT'' more convenient.
 
<code><nowiki>dchroot</nowiki></code> makes it possible to use your newly-built chroot even as a non-root user.  Hence, you can configure your chroot environment in such a way that you can even use your existing <code><nowiki>/home</nowiki></code> as the chroot's <code><nowiki>/home</nowiki></code>, thereby saving you some expensive moving in between homes, as well as making package building/testing a ''LOT'' more convenient.
−
 
 
To do this, first fix the user and root password:
 
To do this, first fix the user and root password:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo cp /etc/passwd /var/chroot/etc/
 
sudo cp /etc/passwd /var/chroot/etc/
第89行： 第64行：
 
sudo cp /etc/hosts /var/chroot/etc/ # avoid sudo warnings when it tries to resolve the chroot's hostname
 
sudo cp /etc/hosts /var/chroot/etc/ # avoid sudo warnings when it tries to resolve the chroot's hostname
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
Then enable sudo and setup your passwords for root and the first sudo user in the `admin` group:
 
Then enable sudo and setup your passwords for root and the first sudo user in the `admin` group:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo cp /etc/sudoers /var/chroot/etc/
 
sudo cp /etc/sudoers /var/chroot/etc/
第98行： 第71行：
 
passwd <your first ubuntu user in the admin group>
 
passwd <your first ubuntu user in the admin group>
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
Next, install the [http://packages.ubuntu.com/sudo sudo] package to be able to use it being in chroot:
 
Next, install the [http://packages.ubuntu.com/sudo sudo] package to be able to use it being in chroot:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
apt-get install sudo
 
apt-get install sudo
 
exit
 
exit
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
Finish things up:
 
Finish things up:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo editor /etc/fstab
 
sudo editor /etc/fstab
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
Add these lines: (/media/cdrom is optional, of course, and you might have to create the dir in the chroot)
 
Add these lines: (/media/cdrom is optional, of course, and you might have to create the dir in the chroot)
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
/home          /var/chroot/home        none    bind            0      0
 
/home          /var/chroot/home        none    bind            0      0
第122行： 第89行：
 
devpts-chroot  /var/chroot/dev/pts    devpts  defaults        0      0
 
devpts-chroot  /var/chroot/dev/pts    devpts  defaults        0      0
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
Mount them:
 
Mount them:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo mount -a
 
sudo mount -a
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
The default bash path includes chroot information.  To make this visible:
 
The default bash path includes chroot information.  To make this visible:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo chroot /var/chroot/
 
sudo chroot /var/chroot/
第136行： 第99行：
 
exit
 
exit
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
Now when you want to use your chroot (you may omit the <code><nowiki>-c mychroot</nowiki></code> if there's only one, or you just want the first one in the file). The <code><nowiki>-d</nowiki></code> parameter means that your environment will be preserved, this is generally useful if you want chrooted applications to seamlessly use your X server, your session manager, etc.
 
Now when you want to use your chroot (you may omit the <code><nowiki>-c mychroot</nowiki></code> if there's only one, or you just want the first one in the file). The <code><nowiki>-d</nowiki></code> parameter means that your environment will be preserved, this is generally useful if you want chrooted applications to seamlessly use your X server, your session manager, etc.
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
dchroot -c mychroot -d
 
dchroot -c mychroot -d
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
Tada!  Now you can switch to and from your main <code><nowiki>/</nowiki></code> and <code><nowiki>/var/chroot/</nowiki></code>, without even becoming root!
 
Tada!  Now you can switch to and from your main <code><nowiki>/</nowiki></code> and <code><nowiki>/var/chroot/</nowiki></code>, without even becoming root!
−
 
−
 
 
==== Shortcuts / Usage ====
 
==== Shortcuts / Usage ====
−
 
 
you can type dchroot -d "command" and it executes that command in the chroot.
 
you can type dchroot -d "command" and it executes that command in the chroot.
−
 
 
I have this script do_chroot in /usr/local/bin:
 
I have this script do_chroot in /usr/local/bin:
 
<pre><nowiki>
 
<pre><nowiki>
第155行： 第111行：
 
/usr/bin/dchroot -d "`echo $0 | sed 's|^.*/||'` $*"
 
/usr/bin/dchroot -d "`echo $0 | sed 's|^.*/||'` $*"
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
''I had trouble with quoting in the above script.  This one works better for me. ~JPKotta''
 
''I had trouble with quoting in the above script.  This one works better for me. ~JPKotta''
 
<pre><nowiki>
 
<pre><nowiki>
第162行： 第117行：
 
args="$args '$i'"
 
args="$args '$i'"
 
done
 
done
−
 
 
/usr/bin/dchroot -d -- "$0" "$args"
 
/usr/bin/dchroot -d -- "$0" "$args"
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
Then I create a symbolic link from that to the command I want to execute in the chroot, e.g.:
 
Then I create a symbolic link from that to the command I want to execute in the chroot, e.g.:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
ln -s /usr/local/bin/do_chroot /usr/local/bin/firefox
 
ln -s /usr/local/bin/do_chroot /usr/local/bin/firefox
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
which will execute firefox in the chroot environment when I launch it in my normal 64 bit environment. To launch my amd64 firefox I can type /usr/bin/firefox.
 
which will execute firefox in the chroot environment when I launch it in my normal 64 bit environment. To launch my amd64 firefox I can type /usr/bin/firefox.
−
 
 
Instead if you want you can just create a script for launching the 32bit firefox e.g.:
 
Instead if you want you can just create a script for launching the 32bit firefox e.g.:
−
 
 
<pre><nowiki>
 
<pre><nowiki>
 
#!/bin/bash
 
#!/bin/bash
 
dchroot -d "firefox"
 
dchroot -d "firefox"
 
</nowiki></pre>
 
</nowiki></pre>
−
 
 
put it in /usr/local/bin and add it to the gnome menu.
 
put it in /usr/local/bin and add it to the gnome menu.
−
 
 
If you're going to start a program that only works in 32bit, first type dchroot -d and you'll be in the 32 bit environment.
 
If you're going to start a program that only works in 32bit, first type dchroot -d and you'll be in the 32 bit environment.
−
 
 
=== Notes ===
 
=== Notes ===
−
 
 
Some missing points are covered on this external article: http://ornellas.apanela.com/dokuwiki/pub:multiarch.
 
Some missing points are covered on this external article: http://ornellas.apanela.com/dokuwiki/pub:multiarch.
−
 
 
From unknown Sun Apr 17 05:43:14 +0100 2005
 
From unknown Sun Apr 17 05:43:14 +0100 2005
 
From:  
 
From:  
第194行： 第138行：
 
Subject: Using symlinks for passwd, groups, shadow, etc..?
 
Subject: Using symlinks for passwd, groups, shadow, etc..?
 
Message-ID: <20050417054314+0100@https://www.ubuntulinux.org>
 
Message-ID: <20050417054314+0100@https://www.ubuntulinux.org>
−
 
 
Wouldn't it be possible to use symlinks for the files that get copied into the chroot?
 
Wouldn't it be possible to use symlinks for the files that get copied into the chroot?
 
Like /etc/hosts? Would it work with /etc/passwd and the like?
 
Like /etc/hosts? Would it work with /etc/passwd and the like?
−
 
 
From MichaelShigorin Sun Apr 17 13:42:38 +0100 2005
 
From MichaelShigorin Sun Apr 17 13:42:38 +0100 2005
 
From: Michael Shigorin
 
From: Michael Shigorin
第203行： 第145行：
 
Subject: nope
 
Subject: nope
 
Message-ID: <20050417134238+0100@https://www.ubuntulinux.org>
 
Message-ID: <20050417134238+0100@https://www.ubuntulinux.org>
−
 
 
...but you can mount --bind them one be one. :)
 
...but you can mount --bind them one be one. :)
−
 
 
From goofrider Thu May 12 19:26:45 +0100 2005
 
From goofrider Thu May 12 19:26:45 +0100 2005
 
From: goofrider
 
From: goofrider
第211行： 第151行：
 
Subject: chroot and symlinks
 
Subject: chroot and symlinks
 
Message-ID: <20050512192645+0100@https://www.ubuntulinux.org>
 
Message-ID: <20050512192645+0100@https://www.ubuntulinux.org>
−
 
 
You can't symlinks from inside the chroot to somewhere outside of it, because once you chroot into it, the new chroot will becomes `/`, and all symlinks will be resolved relative to this new `/`. Use `mount --bind` instead (though hard links should work too).  --GoofRider 2005-05-12
 
You can't symlinks from inside the chroot to somewhere outside of it, because once you chroot into it, the new chroot will becomes `/`, and all symlinks will be resolved relative to this new `/`. Use `mount --bind` instead (though hard links should work too).  --GoofRider 2005-05-12
−
 
 
From Sam Fri May 13 09:22:44 +0100 2005
 
From Sam Fri May 13 09:22:44 +0100 2005
 
From: Sam
 
From: Sam
第219行： 第157行：
 
Subject: mount -a
 
Subject: mount -a
 
Message-ID: <[email protected]>
 
Message-ID: <[email protected]>
−
 
 
You can use
 
You can use
 
$ sudo mount -a
 
$ sudo mount -a
 
for mounting all the entries in fstab instead of mounting them one by one.
 
for mounting all the entries in fstab instead of mounting them one by one.
−
 
 
From LukaszStelmach Sun May 15 00:06:59 +0100 2005
 
From LukaszStelmach Sun May 15 00:06:59 +0100 2005
 
From: Lukasz Stelmach
 
From: Lukasz Stelmach
第229行： 第165行：
 
Subject: Using symlinks
 
Subject: Using symlinks
 
Message-ID: <[email protected]>
 
Message-ID: <[email protected]>
−
 
 
You can make hardlink to files (but only when your chroot dir is on te same partition):
 
You can make hardlink to files (but only when your chroot dir is on te same partition):
−
 
 
ln /etc/passwd /var/chroot/etc/
 
ln /etc/passwd /var/chroot/etc/
−
 
 
From: Elmo, 21.12.05
 
From: Elmo, 21.12.05
 
Does anyone know howto enable DRI from inside a 32bit chroot, 'cause if I mount --bind /dev/dri chroot/dev/dri I get the following error: "DDX driver parameter mismatch: got 848 bytes, but expected 840 bytes.
 
Does anyone know howto enable DRI from inside a 32bit chroot, 'cause if I mount --bind /dev/dri chroot/dev/dri I get the following error: "DDX driver parameter mismatch: got 848 bytes, but expected 840 bytes.
 
libGL error: InitDriver failed" (glxinfo)
 
libGL error: InitDriver failed" (glxinfo)
 
I'd really like to get doom3 working on my amd64 install.
 
I'd really like to get doom3 working on my amd64 install.
−
 
 
26.12.05, Elmo:
 
26.12.05, Elmo:
 
I know, it should work natively, but I have problems with other games aswell, so getting dri working from a chroot would be great=)
 
I know, it should work natively, but I have problems with other games aswell, so getting dri working from a chroot would be great=)
−
 
 
26.12.05, Elmo:
 
26.12.05, Elmo:
 
At debian-amd64 list(http://lists.debian.org/debian-amd64/2005/02/msg00807.html), around February 05, is said that it's not possible at the moment. Got to find another way around my problem, will propably post to ubuntu forums.
 
At debian-amd64 list(http://lists.debian.org/debian-amd64/2005/02/msg00807.html), around February 05, is said that it's not possible at the moment. Got to find another way around my problem, will propably post to ubuntu forums.
−
 
−
 
 
10.06.06 Just a note from a person who ruined his system: After all this is done do not go and delete things from /var/chroot willy-nilly as it will delete the files from the linked directory as well. I found this out only after my entire /home directory was wiped out when I tried to free up some disk space by deleting the files from the chroot directory. Thanks to my foolishness I emptied root's trash before I realized what I'd done. It's been a while since my last backup so I lost everything from Documents, etc for the last year or so.
 
10.06.06 Just a note from a person who ruined his system: After all this is done do not go and delete things from /var/chroot willy-nilly as it will delete the files from the linked directory as well. I found this out only after my entire /home directory was wiped out when I tried to free up some disk space by deleting the files from the chroot directory. Thanks to my foolishness I emptied root's trash before I realized what I'd done. It's been a while since my last backup so I lost everything from Documents, etc for the last year or so.
−
 
 
From: Murray Cumming 06.10.05:
 
From: Murray Cumming 06.10.05:
 
I had to do "apt-get install language-pack-en" to avoid the "Locale not supported by C library." warnings. Even "sudo dpkg-reconfigure locales" gave a "perl: warning: Setting locale failed." error until I did this. And that was even after I did a whole "sudo apt-get ubuntu-desktop" in the chroot.
 
I had to do "apt-get install language-pack-en" to avoid the "Locale not supported by C library." warnings. Even "sudo dpkg-reconfigure locales" gave a "perl: warning: Setting locale failed." error until I did this. And that was even after I did a whole "sudo apt-get ubuntu-desktop" in the chroot.
  
 
[[category:UbuntuHelp]]
 
[[category:UbuntuHelp]]

2007年11月30日 (五) 16:40的版本

Geographylogo.png 文章出处: 

https://help.ubuntu.com/community/DebootstrapChroot

Geographylogo.png 点击翻译: 

English  • 中文

请不要直接编辑翻译本页，本页将定期与来源同步。


DebootstrapChroot

This article shows you how to use debootstrap to build a chroot environment that you can use for various needs, from trying out the latest (or even oldest ;) Ubuntu releases, or even working with Debian releases, to utilizing the chroot as a package building environment. You can work anywhere - this Howto will assume you're using /var/chroot . It will also assume that you want to install a BreezyBadger chroot; if you are going to use other Ubuntu releases, replace breezy below with warty for WartyWarthog, hoary for HoaryHedgehog, dapper for DapperDrake, edgy for EdgyEft, or "feisty" for FeistyFawn.

Getting and installing debootstrap

For the least pain and gnashing of teeth, please get the Ubuntu binary packages manually:

Example: Terminal session wget-ing and installing the latest Feisty debootstrap: 

wget http://archive.ubuntu.com/ubuntu/pool/main/d/debootstrap/debootstrap_0.3.3.2ubuntu3_all.deb
sudo dpkg --install debootstrap_0.3.3.2ubuntu3_all.deb

Installing and configuring dchroot

dchroot is a convenient means of managing chroot environments; with this tool you can have both Breezy, Dapper, and even Debian Sid chroots in your Ubuntu install, and using a chroot environment is a simple as dchroot -c dapper -d ;) To get it dchroot working in your system, just do the following in a Terminal: 

sudo apt-get install dchroot
sudo mkdir /var/chroot # Remember, we assume our chroot is here
sudo editor /etc/dchroot.conf

Then append this line in /etc/dchroot.conf: 

mychroot /var/chroot

Setting up your chroot with debootstrap

If you want a 32-bit chroot on amd64 add --arch i386 to this command line. If you use the chroot to build packages add --variant=buildd . Change breezy to according to your needs to warty, hoary, or dapper, or leave as is for breezy chroot. To actually install the base chroot, open a Terminal and do: 

sudo debootstrap --variant=buildd --arch i386 breezy /var/chroot/ http://archive.ubuntu.com/ubuntu/

debootstrap will then build a BreezyBadger chroot in /var/chroot/, getting the base packages in http://archive.ubuntu.com/ubuntu/, and, depending on the given additional options (in square brackets,) debootstrap will build a chroot for the given architecture and variant. If debootstrap finishes successfully, you'll be left with a base chroot in /var/chroot, which is, well, hardly suitable for anything very interesting. To actually get our chroot to work and be able to, say, grab packages from the network, do the following right after debootstrap: 

sudo cp /etc/resolv.conf /var/chroot/etc/resolv.conf
sudo cp /etc/apt/sources.list /var/chroot/etc/apt/
sudo sed -i s/dapper/breezy/g /var/chroot/etc/apt/sources.list #point apt-get to the right release
sudo chroot /var/chroot/
mount /proc
apt-get update
apt-get install wget debconf devscripts gnupg nano  #For package-building
apt-get update  #clean the gpg error message
apt-get install locales dialog  #If you don't talk en_US 
locale-gen en_GB.UTF-8  # or your preferred locale
tzselect; TZ='Continent/Country'; export TZ  #Configure and use our local time instead of UTC; save in .profile
exit

You can stop here if you want and have a simple chroot that you use as root (sudo chroot /var/chroot). If you want to use your chroot as another user and have access to your normal /home etc inside the chroot, carry on ;) If you want to build a Debian chroot on an Ubuntu system you need to point it at a Debian archive: 

sudo debootstrap --arch i386 sid sid/ http://ftp.uk.debian.org/debian/

Setting up a dchroot (non-root) environment

dchroot makes it possible to use your newly-built chroot even as a non-root user. Hence, you can configure your chroot environment in such a way that you can even use your existing /home as the chroot's /home, thereby saving you some expensive moving in between homes, as well as making package building/testing a LOT more convenient. To do this, first fix the user and root password: 

sudo cp /etc/passwd /var/chroot/etc/
sudo sed 's/\([<sup>:]*\):[</sup>:]*:/\1:*:/' /etc/shadow | sudo tee /var/chroot/etc/shadow
sudo cp /etc/group /var/chroot/etc/
sudo cp /etc/hosts /var/chroot/etc/ # avoid sudo warnings when it tries to resolve the chroot's hostname

Then enable sudo and setup your passwords for root and the first sudo user in the `admin` group: 

sudo cp /etc/sudoers /var/chroot/etc/
sudo chroot /var/chroot/
dpkg-reconfigure passwd
passwd <your first ubuntu user in the admin group>

Next, install the sudo package to be able to use it being in chroot: 

apt-get install sudo
exit

Finish things up: 

sudo editor /etc/fstab

Add these lines: (/media/cdrom is optional, of course, and you might have to create the dir in the chroot) 

/home           /var/chroot/home        none    bind            0       0
/tmp            /var/chroot/tmp         none    bind            0       0
/media/cdrom    /var/chroot/media/cdrom none    bind            0       0
/dev            /var/chroot/dev         none    bind            0       0 
proc-chroot     /var/chroot/proc        proc    defaults        0       0
devpts-chroot   /var/chroot/dev/pts     devpts  defaults        0       0

Mount them: 

sudo mount -a

The default bash path includes chroot information. To make this visible: 

sudo chroot /var/chroot/
echo mychroot > etc/debian_chroot
exit

Now when you want to use your chroot (you may omit the -c mychroot if there's only one, or you just want the first one in the file). The -d parameter means that your environment will be preserved, this is generally useful if you want chrooted applications to seamlessly use your X server, your session manager, etc. 

dchroot -c mychroot -d

Tada! Now you can switch to and from your main / and /var/chroot/, without even becoming root!

Shortcuts / Usage

you can type dchroot -d "command" and it executes that command in the chroot. I have this script do_chroot in /usr/local/bin: 

#!/bin/sh
/usr/bin/dchroot -d "`echo $0 | sed 's|^.*/||'` $*"

I had trouble with quoting in the above script. This one works better for me. ~JPKotta 

args=""
for i in "$@" ; do 
args="$args '$i'"
done
/usr/bin/dchroot -d -- "$0" "$args"

Then I create a symbolic link from that to the command I want to execute in the chroot, e.g.: 

ln -s /usr/local/bin/do_chroot /usr/local/bin/firefox

which will execute firefox in the chroot environment when I launch it in my normal 64 bit environment. To launch my amd64 firefox I can type /usr/bin/firefox. Instead if you want you can just create a script for launching the 32bit firefox e.g.: 

#!/bin/bash
dchroot -d "firefox"

put it in /usr/local/bin and add it to the gnome menu. If you're going to start a program that only works in 32bit, first type dchroot -d and you'll be in the 32 bit environment.

Notes

Some missing points are covered on this external article: http://ornellas.apanela.com/dokuwiki/pub:multiarch. From unknown Sun Apr 17 05:43:14 +0100 2005 From: Date: Sun, 17 Apr 2005 05:43:14 +0100 Subject: Using symlinks for passwd, groups, shadow, etc..? Message-ID: <20050417054314+0100@https://www.ubuntulinux.org> Wouldn't it be possible to use symlinks for the files that get copied into the chroot? Like /etc/hosts? Would it work with /etc/passwd and the like? From MichaelShigorin Sun Apr 17 13:42:38 +0100 2005 From: Michael Shigorin Date: Sun, 17 Apr 2005 13:42:38 +0100 Subject: nope Message-ID: <20050417134238+0100@https://www.ubuntulinux.org> ...but you can mount --bind them one be one. :) From goofrider Thu May 12 19:26:45 +0100 2005 From: goofrider Date: Thu, 12 May 2005 19:26:45 +0100 Subject: chroot and symlinks Message-ID: <20050512192645+0100@https://www.ubuntulinux.org> You can't symlinks from inside the chroot to somewhere outside of it, because once you chroot into it, the new chroot will becomes `/`, and all symlinks will be resolved relative to this new `/`. Use `mount --bind` instead (though hard links should work too). --GoofRider 2005-05-12 From Sam Fri May 13 09:22:44 +0100 2005 From: Sam Date: Fri, 13 May 2005 09:22:44 +0100 Subject: mount -a Message-ID: <[email protected]> You can use $ sudo mount -a for mounting all the entries in fstab instead of mounting them one by one. From LukaszStelmach Sun May 15 00:06:59 +0100 2005 From: Lukasz Stelmach Date: Sun, 15 May 2005 00:06:59 +0100 Subject: Using symlinks Message-ID: <[email protected]> You can make hardlink to files (but only when your chroot dir is on te same partition): ln /etc/passwd /var/chroot/etc/ From: Elmo, 21.12.05 Does anyone know howto enable DRI from inside a 32bit chroot, 'cause if I mount --bind /dev/dri chroot/dev/dri I get the following error: "DDX driver parameter mismatch: got 848 bytes, but expected 840 bytes. libGL error: InitDriver failed" (glxinfo) I'd really like to get doom3 working on my amd64 install. 26.12.05, Elmo: I know, it should work natively, but I have problems with other games aswell, so getting dri working from a chroot would be great=) 26.12.05, Elmo: At debian-amd64 list(http://lists.debian.org/debian-amd64/2005/02/msg00807.html), around February 05, is said that it's not possible at the moment. Got to find another way around my problem, will propably post to ubuntu forums. 10.06.06 Just a note from a person who ruined his system: After all this is done do not go and delete things from /var/chroot willy-nilly as it will delete the files from the linked directory as well. I found this out only after my entire /home directory was wiped out when I tried to free up some disk space by deleting the files from the chroot directory. Thanks to my foolishness I emptied root's trash before I realized what I'd done. It's been a while since my last backup so I lost everything from Documents, etc for the last year or so. From: Murray Cumming 06.10.05: I had to do "apt-get install language-pack-en" to avoid the "Locale not supported by C library." warnings. Even "sudo dpkg-reconfigure locales" gave a "perl: warning: Setting locale failed." error until I did this. And that was even after I did a whole "sudo apt-get ubuntu-desktop" in the chroot.

取自“https://wiki.ubuntu.org.cn/index.php?title=UbuntuHelp:DebootstrapChroot&oldid=36835”