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 on the profile)
Or maybe to add functionality to make a profile "read-only"? so that container 
function can be preserved
Thank you very much for your kind help

ZF
 

    On Friday, August 12, 2016 12:50 AM, Bug Watch Updater 
<1612...@bugs.launchpad.net> wrote:
 
 

 ** Changed in: lxd
      Status: Unknown => Fix Released

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1612388

Title:
  cannot remove device

Status in lxd:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Committed

Bug description:
  I am trying to create a container without network interface.
  during lxd init I selected not to create a bridge (and it was not created)

  so

  lxc init ubuntu:16.04/amd64 gerecon --profile default

  lxc config device remove    gerecon eth0 
  Device eth0 removed from gerecon
  lxc config device remove    gerecon eth0 
  Device eth0 removed from gerecon

  already seems strange as the second call to remove eth0 claims that it was 
happy to remove it
  after the first call was successfull

  if I try to start the container I get this:

  lxc start gerecon
  error: Error calling 'lxd forkstart gerecon /var/lib/lxd/containers 
/var/log/lxd/gerecon/lxc.conf': err='exit status 1'
  Try `lxc info --show-log gerecon` for more info

  relevant piece of lxc info  is:

  
              lxc 20160811150615.590 ERROR    lxc_conf - 
conf.c:instantiate_veth:2595 - failed to attach 'vethRN05WQ' to the bridge 
'lxdbr0': Operation not permitted
              lxc 20160811150615.591 INFO    lxc_confile - 
confile.c:config_idmap:1500 - read uid map: type u nsid 0 hostid 165536 range 
65536
              lxc 20160811150615.591 INFO    lxc_confile - 
confile.c:config_idmap:1500 - read uid map: type g nsid 0 hostid 165536 range 
65536
              lxc 20160811150615.617 ERROR    lxc_conf - 
conf.c:lxc_create_network:2872 - failed to create netdev
              lxc 20160811150615.617 ERROR    lxc_start - 
start.c:lxc_spawn:1080 - failed to create the network
              lxc 20160811150615.617 ERROR    lxc_start - 
start.c:__lxc_start:1353 - failed to spawn 'gerecon'
              lxc 20160811150615.617 INFO    lxc_conf - 
conf.c:run_script_argv:367 - Executing script 
'/usr/share/lxcfs/lxc.reboot.hook' for container 'gerecon', config section 'lxc'
              lxc 20160811150616.120 INFO    lxc_conf - 
conf.c:run_script_argv:367 - Executing script '/usr/bin/lxd callhook 
/var/lib/lxd 15 stop' for container 'gerecon', config section 'lxc'

  
  as you see, it is trying to connect to the bridge which does not exist using 
network interface which should not exist in the container

  lxc config show  gerecon has this (reference to eth0 which should have
  been removed)

  profiles:
  - default
  config:
    volatile.base_image: 
199e9a37b6aa19a258b89fbbbcf99abb2e00d2b833b00db444da92f202d06ac5
    volatile.eth0.hwaddr: 00:16:3e:bd:70:90


  out of curiosity I did this

  lxc config device set    gerecon eth0 nictype bridged
  error: The device doesn't exist

  
  Am I doing something wrong or this is a bug ?

  thank you very much for your help

  ZF

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxd/+bug/1612388/+subscriptions

-- 
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://bugs.launchpad.net/lxd/+bug/1612388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to