Schroot doesn't mount /home submounts in the chroot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
schroot (Debian) |
New
|
Unknown
|
|||
schroot (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Binary package hint: schroot
My home dir is mounted as /home/wookey. Within the company this is normally a remote dir, but I moved mine to be local to avoid a whole host of pain :-)
Using schroot it mounts /home with bind, rather than rbind, so inside the chroot I cannot see my home dir, only the (nearly empty) /home that has /home/wookey mounted on it. This was extremely confusing for a while as the old /home has a (normally inaccessible) /home/wookey containing nothing much from when the machine was originally set up.
Changing /etc/schroot/
/home /home none rw,bind 0 0
to
/home /home none rw,rbind 0 0
makes it work as expected (my files are visible inside the chroot).
So, in fact it's easy to fix - schroot is very nicely designed; but it took hours to work out what on earth was wrong in the first place. Having a sub-dir mounted as a home dir is quite a common configuration in institutions and larger companies, so this problem will potentially affect a lot of people (who might not even realise that schroot is incredibly cool and should automatically makes all their files available inside the chroot).
So, perhaps rbind should be the default, not bind, for /home? Is there a good reason not to do this?
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: schroot 1.4.17-1
ProcVersionSign
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Thu Jun 2 16:43:42 2011
ProcEnviron:
SHELL=/bin/bash
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
SourcePackage: schroot
UpgradeStatus: Upgraded to natty on 2011-05-23 (9 days ago)
Changed in schroot (Debian): | |
status: | Unknown → New |
Changed in schroot (Ubuntu): | |
status: | New → Confirmed |
Changed in schroot (Debian): | |
status: | New → Won't Fix |
Changed in schroot (Ubuntu): | |
importance: | Undecided → Medium |
Changed in schroot (Ubuntu): | |
status: | Confirmed → Won't Fix |
Changed in schroot (Debian): | |
status: | Won't Fix → New |
I see https:/ /bugs.launchpad .net/ubuntu/ +source/ schroot/ +bug/769595 is essentially asking for the same default.