Marking invalid for LXD as we don't support running on kernels without
seccomp support. Upgrading to linux-generic-lts-xenial should fix this
issue for you (confirmed on a test system).
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
** Changed in: juju-core
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600311
Title:
Juju 2.0 Bootstrap Fails on Ubuntu Trusty Power machine.
To manage
Oh, you said on a trusty host. Then that's your problem.
The release kernel for trusty (3.13) isn't capable of seccomp and so
containers just fail to start.
Upgrade to the 4.4 kernel and things should start working again.
--
You received this bug notification because you are a member of Ubuntu
Since this seems to be a LXD problem please pastebin the following
commands:
sudo lxc list
sudo lxc remote add images images.linuxcontainers.org
sudo lxc launch images:ubuntu/trusty/ppc64el ubuntu-test
sudo lxc list
sudo lxc stop ubuntu-test
sudo lxc delete ubuntu-test
If those commands fail,
3.16 (lts-utopic) and 3.19 (lts-vivid) also are lacking seccomp support,
4.2 (lts-wily) has it I believe but it wasn't tested. 4.4 is what we
test ppc64el with and has been confirmed to have seccomp support.
We have no plans to support other kernels on ppc64el as it'd mean
turning off a critical
The interesting problems here all seem to be at the lxd level, from the
second log in comment #2:
lxc 20160714064249.306 INFO lxc_apparmor -
lsm/apparmor.c:apparmor_process_label_set:238 - changed apparmor profile to
lxd-juju-47a009-0_
lxc 20160714064249.306 ERRORlxc_seccomp -
