[Bug 931220] Re: lxc.conf upstart job fails to spawn containers at boot time

Stéphane Graber stgraber at stgraber.org
Mon Feb 13 18:13:18 UTC 2012


Assigning to Serge at his request ;)

The issue was tracked down to be an inherited fd likely from libldap
passed to libnss-ldap then passed to libnss and eventually to upstart.
This socket isn't marked as CLOEXEC so all processes inherit it.

I'll file a separate bug against upstart to have all the fds closed
before running the jobs, for now though we think it'd be good to have a
close-all-fds option in lxc, possibly making it the default for -d so we
can use it to workaround these issues.

** Changed in: upstart (Ubuntu)
       Status: New => Invalid

** Changed in: lxc (Ubuntu)
       Status: New => Triaged

** Changed in: lxc (Ubuntu)
     Assignee: (unassigned) => Serge Hallyn (serge-hallyn)

** Summary changed:

- lxc.conf upstart job fails to spawn containers at boot time
+ lxc-start should get a close-all-fds option to avoid weird issues

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/931220

Title:
  lxc-start should get a close-all-fds option to avoid weird issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/931220/+subscriptions



More information about the Ubuntu-server-bugs mailing list