kernel-packages team mailing list archive

[Serge Hallyn <1263738@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: lxc (Ubuntu)
     Importance: High
         Status: Triaged

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

-- 
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 “linux” package in Ubuntu:
  New
Status in “lxc” package in Ubuntu:
  Triaged

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/ubuntu/+source/linux/+bug/1263738/+subscriptions