** 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
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:
** 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
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
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
** 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
+
