Thanks for taking the time to report this bug. Is the command in the description exactly the command you used, or did you specify a config file with '-f'? If you specified a config file, can you paste it here?
If you did not specify a config file, then you shoudl have seen a warning like: ===================================================================== Warning: ------- Usually the template option is called with a configuration file option too, mostly to configure the network. eg. lxc-create -n foo -f lxc.conf -t debian The configuration file is often: lxc.network.type=macvlan lxc.network.link=eth0 lxc.network.flags=up or alternatively: lxc.network.type=veth lxc.network.link=br0 lxc.network.flags=up For more information look at lxc.conf (5) At this point, I assume you know what you do. Press <enter> to continue ... ===================================================================== Such a container indeed will fail to start because it will not have a network configuration, and therefore not create a new network namespace, so that the container's upstart shares abstract unix sockets with the host's. It's reasonable for certain containers, but not supported with a full ubuntu container. -- 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/884428 Title: new created ubuntu machines result in: "init: Unable to listen for private connections: Failed to bind socket "/com/ubuntu/upstart": Address already in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/884428/+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
