login console 0 in user namespace container is not configured right
Bug #1263738 reported by
Serge Hallyn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Fix Released
|
Undecided
|
James Hunt | ||
linux (Ubuntu) |
Confirmed
|
High
|
Seth Forshee | ||
Trusty |
Confirmed
|
High
|
Seth Forshee | ||
lxc (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Trusty |
Invalid
|
High
|
Unassigned | ||
upstart (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned |
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://
so also marking this as affecting the kernel.
This can be worked around, but really needs to be fixed before trusty is frozen.
Related branches
lp://staging/~jamesodhunt/upstart/kmsg-noctty
- Stéphane Graber (community): Approve
-
Diff: 76 lines (+37/-14)2 files modifiedChangeLog (+6/-0)
init/main.c (+31/-14)
tags: | added: bot-stop-nagging |
Changed in linux (Ubuntu): | |
status: | Incomplete → New |
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
tags: | added: kernel-key trusty |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | removed: kernel-key |
Changed in upstart: | |
assignee: | nobody → James Hunt (jamesodhunt) |
status: | New → Fix Committed |
Changed in upstart (Ubuntu Trusty): | |
status: | New → Confirmed |
Changed in upstart (Ubuntu Trusty): | |
importance: | Undecided → High |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1263738
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.