starts/stops in containers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
Precise |
Invalid
|
Medium
|
Martin Pitt | ||
Trusty |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
As soon as you start/stop a container, or install/remove apport in the container, apport's init.d/upstart script change the global /proc/sys/
Only the host should set core_pattern, and with https:/
FIX: http://
SRU TEST CASE (stop):
- Check that apport is currently enabled:
$ cat /proc/sys/
|/usr/
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Stop the container:
$ sudo poweroff # within the container
- Apport is now disabled globally:
$ cat /proc/sys/
core
With the fixed apport, /proc/sys/
SRU TEST CASE (start):
- Stop apport globally:
$ sudo stop apport
$ cat /proc/sys/
core
- Start a container (that has apport installed):
$ sudo lxc-start-ephemeral -o precise
- Apport is now globally enabled:
$ cat /proc/sys/
|/usr/
With the fixed apport, /proc/sys/
SRU TEST CASE (regression test):
- Starting/stopping apport manually should still work. After booting, apport should be enabled:
$ cat /proc/sys/
|/usr/
$ sudo stop apport
$ cat /proc/sys/
core
$ sudo start apport
$ cat /proc/sys/
|/usr/
REGRESSION POTENTIAL: In releases < trusty, apport would not work in containers at all, as the kernel calls the host's apport; before https:/
description: | updated |
description: | updated |
Changed in apport (Ubuntu Trusty): | |
assignee: | Martin Pitt (pitti) → nobody |
status: | New → Fix Committed |
assignee: | nobody → Martin Pitt (pitti) |
description: | updated |
Changed in apport (Ubuntu Precise): | |
status: | New → In Progress |
Fixed upstream in http:// bazaar. launchpad. net/~apport- hackers/ apport/ trunk/revision/ 2748, but that's only the init.d script which we don't use in Ubuntu.