[Bug 1047712] Re: container-detect.conf should be 'start on virtual-filesystems'

Scott Moser smoser at ubuntu.com
Sat Sep 8 02:40:35 UTC 2012

marked as also-affects resolvconf as /etc/init/resolvconf.conf also is
start on mounted MOUNTPOINT=/run

** Also affects: resolvconf (Ubuntu)
   Importance: Undecided
       Status: New

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.

  container-detect.conf should be 'start on virtual-filesystems'

Status in “resolvconf” package in Ubuntu:
Status in “upstart” package in Ubuntu:

Bug description:
  I'm running into some issues during my "ephemeral boot" (iscsi read-only root) work for maas.
  In debugging bug 1031065, we had 'cloud-init-nonet' actually mount all virtual-filesystems and then emit the event.

  After doing that, we were still timing out on networking coming up
  because of a dependency on specifically 'mounted mountpoint=/run' by

  changing that to 'start on virtual-filesystems' improves my situation.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: upstart 1.5-0ubuntu8
  ProcVersionSignature: User Name 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sat Sep  8 02:10:46 2012
  Ec2AMI: ami-00000148
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
   PATH=(custom, no user)
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list