[Bug 1648056] Re: Support LXD multiple sub-uid mapping
Launchpad Bug Tracker
1648056 at bugs.launchpad.net
Thu Feb 16 19:10:53 UTC 2017
This bug was fixed in the package nova-lxd - 14.1.0-0ubuntu0.16.10.1
nova-lxd (14.1.0-0ubuntu0.16.10.1) yakkety; urgency=medium
* New upstream version for Openstack Newton (LP: #1649304, #1648056).
-- Chuck Short <zulcss at ubuntu.com> Mon, 12 Dec 2016 10:06:01 -0500
** Changed in: nova-lxd (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
Support LXD multiple sub-uid mapping
Status in OpenStack LXD Charm:
Status in Ubuntu Cloud Archive:
Status in Ubuntu Cloud Archive mitaka series:
Status in Ubuntu Cloud Archive newton series:
Status in Ubuntu Cloud Archive ocata series:
Status in nova-lxd:
Status in nova-lxd package in Ubuntu:
Status in nova-lxd source package in Xenial:
Status in nova-lxd source package in Yakkety:
Status in nova-lxd source package in Zesty:
By default, all LXD containers will run with the same subuid/subgid range, which means that if a single container is compromised, all containers on the same host are potentially compromised as well.
deploy a nova-lxd based openstack cloud
boot multiple instances
they all share the same uid/gid mapping within a host
boot multiple instances with a flavor property of lxd:isolated
all containers have different uid/gid mappings within a host
Minimal in nova-lxd itself; we're just adding an additional extra-spec and tweaking the container profile if the underlying LXD daemon supports the isolation feature.
[Original Bug Report]
LXD 2.0.6 supports use of distinct sub-uid/gid for each running container; nova-lxd has support for this upstream in all stable and master branches so we should update nova-lxd in >= Xenial to support this feature.
To manage notifications about this bug go to:
More information about the Ubuntu-openstack-bugs