[Bug 430224] Re: init: support chroots

[Clint Byrum]

Excerpts from Rolf Leggewie's message of Sun Jul 17 09:09:58 UTC 2011:
> Clynt, thank you for taking this up.
> 
> My point is essentially the same as was raised by Lukas in comment 27.
> We need to be sure that a lucid guest will work no matter the host OS.
> I'm not opposed to a PPA workaround but IMHO some code should be added
> probably to dapper somewhere to make sure that if it's detected that
> dapper is running inside a chroot/vserver an update to lucid is not
> performed without that PPA workaround.  Or else the user will run into
> the situation where the vserver is completely unreachable because ssh is
> down (happened to me, booh!).
> 
> I will have to say that I'm a bit disappointed this wasn't taken into
> account seriously much earlier.  The warnings were there early enough.
> 
> Your PPA was building packages for natty right?  I'm not sure what
> direction it is you're taking there, but I'm sure you will let me know.
> Are you trying to fix the host side?

I want to provide a chroot-capable upstart for all relevant versions
of Ubuntu, namely maverick and lucid (natty has chroot support). Hardy
isn't going to happen, as, while it has upstart, that version of upstart
is incompatible with the versions in 10.04 and later. That does mean that
you won't be able to use Hardy to host chroots for anything after it. For
that, you might want to look into the "upstart-dummy" program here:

http://blogs.balabit.com/2011/01/21/using-upstart-in-a-chroot/

We test what we can, and respond to what is raised. Sometimes the rapid
pace of development causes a situation like this, where a fundamental
change is made and users only have 1 cycle to test it out (IIRC, ssh was
moved to upstart in 9.10). This situation is at least going to be handled
in 12.04, so you should be safe in waiting for it, and then leap frogging
to it by upgrading to 10.04 first (sorry not sure if your ssh will work)
and then to 12.04.

So right now, I'd suggest running tests in 11.04, to make sure we actually
solved your problem and don't just think we did.

Anyway, the PPA is still empty because the packages haven't been able
to build yet, but I'll keep working on it.. watch the PPA and here
for updates.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/430224

Title:
  init: support chroots

Status in Release Notes for Ubuntu:
  Fix Released
Status in Upstart:
  Fix Released
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Karmic:
  Won't Fix

Bug description:
  Binary package hint: upstart

  $ sudo chroot /media/karmic dpkg --configure -a
  Setting up cups (1.4.1-1) ...
  update-rc.d: warning: /etc/init.d/cups missing LSB information
  update-rc.d: see <http://wiki.debian.org/LSBInitScripts>
  Rather than invoking init scripts through /etc/init.d, use the service(8)
  utility, e.g. service cups start

  Since the script you are attempting to invoke has been converted to an
  Upstart job, you may also use the start(8) utility, e.g. start cups
  start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
  invoke-rc.d: initscript cups, action "start" failed.
  dpkg: error processing cups (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   cups

  
  WORKAROUND: Create an executable /media/karmic/usr/sbin/policy-rc.d with this in it:
  #!/bin/sh
  exit 101

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/430224/+subscriptions