Marking as invalid per comment #2.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
+ =
+ ec2-run-instances ami-3021fb58 -t m1.small
+
+ ssh into the instance,
+
+ sudo ip link add type veth
+
Serge I don't have the problem now. But there was a round of sw upgrades
during that time and I suspect
whatever had caused it was fixed somewhere.
The original AMI though should still exhibit the problem I guess.
*ubuntu-utopic-14.10-beta1-amd64-server-20140826 (ami-3021fb58)*
Brian
On Tue,
Thanks for submitting this bug.
To be clear,
'sudo ip link add type veth'
also returns an error?
Could you tell us which ami and which machine type you used to start the
amazon instance?
** Changed in: lxc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification becaus
** Package changed: ubuntu => lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373981
Title:
ubuntu 14.10 server, amd64 - lxc-start fails to start container
To manage notifications about
junk this bug report. Latest update for ubuntu 14.10 fixed the lxc
startup problems for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1373981
Title:
ubuntu 14.10 server, amd64 - lxc-start fail
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
