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 (
Dear Stephane
Yes I understad now.
Do you think it would be good to create a mechanism to "detach" the container
from profile with a command. this way the container will preserve its function
even after the profile was changed. (apply all profiles to the container itself
and remove dependence o
** 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/1612388
Title:
cannot remove device
To manage notifications about this bug go to:
https://bug
** 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
** Changed in: lxd (Ubuntu)
Status: New => Fix Committed
** Changed in: lxd (Ubuntu)
Impo
The easiest way to do all of that is with "lxc config edit " which will start an editor that lets you edit all the container
settings, including the list of profiles that are applied to it,
container configuration and the list of devices.
You can absolutely do "lxc profile edit " and copy/paste
th
Is there a mechanims to "deatch" a container from profile?
say to a container aaaContainer was created with bbbProfile. Is it possible to
"transfer" the configuration
from the profile to the container so if the bbbProfile is modified the
aaaContainer does not
change its behaviour?
--
You recei
Exactly! If you modify the default profile, all containers using that
profile will be immediately modified by LXD.
So yeah, the only thing that we really need to fix in LXD is return an
error when you're attempting to remove a device which doesn't exist.
I've sent a patch for this upstream, it's g
Daer Stephane
I thought the device does exist in the default profile...
I can see the hardware address for eth0
Oh
The device is attached to the profile and thus affects all containers
which use the profile
so if I modify the profile all containers will be affected
to modify one container only
Right, so the problem is that "lxc config device remove" says that it
worked when the device you asked to remove from the container doesn't
actually exist.
Your container doesn't actually have that device, one of its profile
does, so that's why you can't remove it from the container.
Instead you
