*** This bug is a duplicate of bug 1240757 *** https://bugs.launchpad.net/bugs/1240757
I had missed restart lxc-net. Unfortunately, that didn't make any difference. kevin@awabi:~$ sudo lxc-start -n escale_build --logfile /tmp/lxc-log --logpriority 3 -F lxc-start: conf.c: instantiate_veth: 2621 failed to attach 'vethKW0GNU' 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. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs