[Bug 884428] Re: new created ubuntu machines result in: init: Unable to listen for private connections: Failed to bind socket /com/ubuntu/upstart: Address already in use
** Changed in: lxc (Ubuntu) Importance: Undecided = High -- 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
[Bug 884428] Re: new created ubuntu machines result in: init: Unable to listen for private connections: Failed to bind socket /com/ubuntu/upstart: Address already in use
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
[Bug 884428] Re: new created ubuntu machines result in: init: Unable to listen for private connections: Failed to bind socket /com/ubuntu/upstart: Address already in use
** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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
[Bug 884428] Re: new created ubuntu machines result in: init: Unable to listen for private connections: Failed to bind socket /com/ubuntu/upstart: Address already in use
Hi Serge, adding the network interface fixed it. Sorry... but I thought that it should be possible to start a machine without a network interface connected to it... Tanks, Lars -- 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
[Bug 884428] Re: new created ubuntu machines result in: init: Unable to listen for private connections: Failed to bind socket /com/ubuntu/upstart: Address already in use
If you want a container with no network interface at all, then you can place the following into your config: lxc.network.type = empty That will create an empty private network namespace. However what you cannot do (due to how upstart works) is have a full ubuntu container sharing the network interface with the host. ** Changed in: lxc (Ubuntu) Status: Incomplete = Invalid -- 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
[Bug 884428] Re: new created ubuntu machines result in: init: Unable to listen for private connections: Failed to bind socket /com/ubuntu/upstart: Address already in use
** Description changed: Created new machine with: lxc-create -n test -t ubuntu -- -r oneiric + + The machine hangs on lxc-start with the message. + + lars@wiesel:~$ ps -elf | grep lxc-star[t] + 4 S root 28932 31912 0 80 0 - 596 ep_pol 22:10 pts/800:00:00 lxc-start -n test + lars@wiesel:~$ pstree -p 28932 + lxc-start(28932)───init(28933)─┬─plymouthd(28944) +└─ureadahead(28948) Old lxc containers still working. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lxc 0.7.5-0ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-12.21~ppa3~loms~oneiric-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Mon Oct 31 22:04:19 2011 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: - PATH=(custom, no user) - LANG=de_DE.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to oneiric on 2011-09-13 (48 days ago) -- 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
