** Changed in: lxd
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574158
Title:
lxd config device add fails with nested containers
To manage notifications abo
This bug was fixed in the package lxd - 2.0.4-0ubuntu2
---
lxd (2.0.4-0ubuntu2) yakkety; urgency=medium
* Cherry-pick from upstream:
- 0002-Fix-for-newer-shellcheck (Fixes adt with yakkety's shellcheck)
-- Stéphane Graber Tue, 16 Aug 2016 15:00:49
-0400
** Changed in: lxd (
** Changed in: lxd (Ubuntu)
Status: Triaged => 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/1574158
Title:
lxd config device add fails with nested containers
To manage notific
** Bug watch added: LXD bug tracker #2279
https://github.com/lxc/lxd/issues/2279
** Also affects: lxd via
https://github.com/lxc/lxd/issues/2279
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** No longer affects: lxd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574158
Title:
lxd config device add fails with nested containers
To manage notifications about this bug go to:
https://bugs.
** Changed in: lxd
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574158
Title:
lxd config device add fails with nested containers
To manage notifications abo
** Bug watch added: LXD bug tracker #2277
https://github.com/lxc/lxd/issues/2277
** Also affects: lxd via
https://github.com/lxc/lxd/issues/2277
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: lxd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574158
Title:
lxd config device add fails with nested containers
To manage notifications a
There is the /dev/lxd interface which could be extended to allow such
things, but we'd have to think through this very very closely to make
this safe.
We absolutely do not want an unprivileged container to have access to an
interface which will cause the host to expose any device it wants over
to
Do containers ever communicate back out to their host for services? If
so, perhaps the 1st-level container could ask the host lxd to help it to
pass on the device? I know lxd is at least aware when its nested and
unprivileged since "lxd init" mentions this; perhaps communication to
the outside migh
That'd be because the unprivileged container cannot run mknod to create
the entry. Though Since you are mounting the same device you already
passed through, there may be a chance we could just do a straight bind-
mount rather than completely failing.
The main problem with that approach is that we
11 matches
Mail list logo
