[Bug 1732518] Re: Please re-enable container support in apport

[Stéphane Graber]

Anyway, for the pidns thing, yes, we can change the condition to trip on
either a different pidns or a different mntns and log a message that
this isn't supported, I'm just not seeing much risk with just supporting
it and it would certainly qualify as a bugfix.

The handling in this case isn't particularly controversial either, if we
see we're in the same mntns but pidns differs we just use the global pid
and move on. We know the filesystem will be the same, so it's fine to
call the hooks and write wherever apport usually writes.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1732518

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732518/+subscriptions