This bug was fixed in the package autopkgtest - 3.19
---
autopkgtest (3.19) unstable; urgency=medium
New features/behaviour changes:
* Add adt-virt-lxd runner for LXD. (LP: #1519677)
* Add adt-build-lxd tool for building or updating an LXD image with
standard autopkgtest cus
This is now working rather nicely, and landed in master.
** Changed in: autopkgtest (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519677
Title:
** Changed in: autopkgtest (Ubuntu)
Status: Triaged => In Progress
** Description changed:
LXD is the direction that the LXC project is moving towards, and it has
several nice features that are helpful for autopkgtest: fast container
creation with intelligent caching, support for loc
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519677
Title:
add lxd backend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest
Parking the work in progress here, to avoid it getting lost. This now
works for some basic use cases, but more complex ones and most of the
tests currently fail due to 'lxc exec' not maintaining stdout+stderr and
mangling line endings.
** Patch added: "WIP patch"
https://bugs.launchpad.net/ubu
** Description changed:
LXD is the direction that the LXC project is moving towards, and it has
several nice features that are helpful for autopkgtest: fast container
creation with intelligent caching, support for local images (with
autopkgtest modifications), and seamless support for remo
Alternatively, the config can be set on launch directly:
lxc launch images:ubuntu/xenial/amd64 x1 --config
raw.lxc=lxc.aa_profile=unconfined
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519677
Ti
Some tests need to mount /proc (like pbuilder) or do bind mounts (like
nested LXC), so we need to relax the restrictions. As lxd containers are
unprivileged, the extra apparmor profile is merely a fallback security
layer; users should not be able to do any harm to the host in an unpriv
container.
