Nested lxd containers

Bug #1902256 reported by Simon Richardson
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Undecided
Unassigned

Bug Description

When attempting to use focal (or eoan and greater) and targeting LXD to deploy to containers then it will fail with apparmour errors.

We've spoken with the LXD team and there isn't anything we can do atm.

See: https://discourse.juju.is/t/juju-is-not-using-existing-cloud-for-bundle-deploy-other-issues/3752

At the very least we should show better error messages about this scenario as you have to do some digging to find out why your charm/bundle won't deploy.

Revision history for this message
Javier Añorga (javieranorgab) wrote :

With juju version 2.9.3 and microstack cloud (ussuri 2021-05-01 (233)) nested lxd containers fail, following official Canonical's microstack installation steps and Juju integration (https://microstack.run/docs/using-juju). Note: official steps must be adapted to use focal series to get kubernetes-core deploying without editing the bundle.

Also following this (https://bugs.launchpad.net/juju/+bug/1569106) (with xenial series) I am also experiencing this issue with nested LXD containers.

Revision history for this message
Pen Gale (pengale) wrote :

This is an lxd issue, and not one that can be trivially resolved -- the app armor changes have their own justifications.

There's not too much we can do in Juju, other than implement the better error messaging.

Nested lxd does not work at present.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.