Interesting, I didn't get this in my original testing of the upstart
job.
Do you know which file is open? (ls -l /proc/pid-of-lxc-start/fd
should show it)
The lxc.conf upstart job could, I suppose, explicitly close all fds
under 1024, but in my opinion this is simply a bug in upstart. It
Note that I still can't reproduce this here.
--
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.conf upstart job fails to spawn containers at boot time
To manage
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
Interesting, I didn't get this in my original testing of the upstart
job.
Do you know which file is open? (ls -l /proc/pid-of-lxc-start/fd
should show it)
The lxc.conf upstart job could, I suppose, explicitly close all fds
under 1024, but in my opinion this is simply a bug in upstart. It
Note that I still can't reproduce this here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931220
Title:
lxc.conf upstart job fails to spawn containers at boot time
To manage notifications about
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
