Quoting Trent W. Buck (trentb...@gmail.com): > "Serge E. Hallyn" <serge.hal...@canonical.com> > writes: > > > Quoting Trent W. Buck (t...@cybersource.com.au): > >> I encountered, isolated, and worked around this issue. > >> > >> Symptom: gettys don't start in the container. runlevel(8) reports > >> "unknown" instead of "N 2". > >> > >> Problem: ifupdown 0.6.8ubuntu29.1 introduces this change: > >> > >> ifupdown (0.6.8ubuntu29.1) lucid-proposed; urgency=low > >> > >> * debian/ifupdown.network-interface.conf: Bring up lo manually, so > >> that it > >> comes up even if /etc/network/interfaces is broken (LP: #512253). > >> * debian/ifupdown.upstart.if-up: Don't emit a duplicate net-device-up > >> event for lo here, as network-interface.conf will have taken care > >> of > >> it. > >> > >> For some reason, upstart DOES NOT generate the event, so when this > > > > Purely guessing, but I assume that normally the kernel creates that > > uevent when lo gets set up? But with the container, lo is created > > (and uevent sent) before the container's upstart is running? > > I have no idea. Any diagnostics commands you'd like me to run?
No, that was a question for the people who would know off the top of their heads (Dan Smith, Daniel Lezcano, or Eric Biederman). Else I'll go look in the code. -serge ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users