[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

[Kevin Dalley]

Host is:

Linux awabi 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux


container is:

Linux escalebuild 3.16.0-51-generic #69~14.04.1-Ubuntu SMP Wed Oct 7
15:32:41 UTC 2015 x86_64 GNU/Linux

here is output from my attempt to start:

kevin at awabi:~$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log --logpriority 3
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.
kevin at awabi:~$ less /tmp/lxc-log 
kevin at awabi:~$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log --logpriority 3 -F
lxc-start: conf.c: instantiate_veth: 2621 failed to attach 'vethJ6CTXM' to the bridge 'lxcbr0': Operation not permitted
lxc-start: conf.c: lxc_create_network: 2904 failed to create netdev
lxc-start: start.c: lxc_spawn: 920 failed to create the network
lxc-start: start.c: __lxc_start: 1172 failed to spawn 'escale_build'
lxc-start: lxc_start.c: main: 344 The container failed to start.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1452601

Title:
  vivid container's networking.service fails on boot with signal=PIPE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions