fail to install maas-dhcp in a container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
As we can see from bug 978297.
In precise, apparmor doesn't start in a container.
So in debian/
not call the apparmor_parser command in a container.
/bin/running-
ubuntu@
upstart: /bin/running-
install log
2013-07-03 14:24:28,334 unit:virtual-
2013-07-03 14:24:29,614 unit:virtual-
2013-07-03 14:24:29,616 unit:virtual-
2013-07-03 14:24:29,617 unit:virtual-
2013-07-03 14:24:29,623 unit:virtual-
2013-07-03 14:24:29,631 unit:virtual-
2013-07-03 14:24:29,641 unit:virtual-
subprocess installed post-installation script returned error exit status 234
dpkg: dependency problems prevent configuration of maas-dns:
maas-dns depends on maas-dhcp (= 1.2+bzr1373+
Package maas-dhcp is not configured yet.
dpkg: error processing maas-dns (--configure):
dependency problems - leaving unconfigured
Changed in maas (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Note that as a workaround you can run your container unconfined, and hopefully soon it will be possible to use stacked apparmor profiles.