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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732518 Title: Please re-enable container support in apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732518/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
