[Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
sudo snap refresh should refresh the kernel snap. However the suspected fix will not be in any snap kernel, nor can I atm build you a kernel snap to test with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Actually, this bug was found with Ubuntu all-snap version. So I am not able to try the kernel.deb. Could you tell me how to get the latest version of the kernel snap for 16.04? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Ignore the request to test the upstream kernel, for the moment. In this case the apparmor code that is in the trace does not exist upstream. Instead could you test the kernel in http://people.canonical.com/~jj/lp1648143/ While listed as being for bug 1648143, it contains several fixes including a fix to the bind mount code. That will be pushed up to the ubuntu kernel this week. If this still exhibits the fault then, please test the upstream kernel to verify that the bug is indeed in apparmor, and not being triggered else where and showing up in apparmor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc2 ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
I added linux back due to the uncanny resemblance to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508737 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586997 Thanks ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Changed the target to be apparmor because the kernel panic is triggered by apparmor. ** Package changed: linux (Ubuntu) => apparmor (Ubuntu) ** Also affects: apparmor Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
The bug was found on the all-snap image. Therefore I was not able to run apport-collect command. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
