So the error suggests that the needed apparmor profile couldn't be found
at the time the container started but there's nothing very definitive in
any of the logs as to why that would be.
It reminds me of an occasional kernel bug that we've been running into
with regard to apparmor namespacing handling but that usually comes with
a kernel log trace and I'm not seeing any in your case.
What's that environment like? Are all those containers running on the
host directly or are they nested?
** Changed in: lxd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667444
Title:
Failed to start lxd container because it is already running a start
operation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1667444/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
