kernel-packages team mailing list archive

[Brian Murray <brian@xxxxxxxxxx>]

This seems to be fixed the in the trusty version of upstart, although no
debian/changelog entry was created for this bug.

** Changed in: upstart
       Status: Fix Committed => Fix Released

** Changed in: upstart (Ubuntu Trusty)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1263738

Title:
  login console 0 in user namespace container is not configured right

Status in Upstart:
  Fix Released
Status in “linux” package in Ubuntu:
  Confirmed
Status in “lxc” package in Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Confirmed
Status in “lxc” source package in Trusty:
  Invalid
Status in “upstart” source package in Trusty:
  Fix Released

Bug description:
  When you create a container in a private user namespace, when you start the
  container without the '-d' flag, that console is not properly set up.  Logging in
  gives you

  -bash: no job control in this shell

  and hitting ctrl-c reboots the container.

  Consoles from 'lxc-console -n $container' behave correctly.

  This may be a kernel issue, as discussed here:

  http://lists.linuxcontainers.org/pipermail/lxc-
  devel/2013-October/005843.html

  so also marking this as affecting the kernel.

  This can be worked around, but really needs to be fixed before trusty
  is frozen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1263738/+subscriptions