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, Sep 30, 2014 at 3:39 PM, Serge Hallyn <1373...@bugs.launchpad.net> wrote: > 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 because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1373981 > > Title: > ubuntu 14.10 server, amd64 - lxc-start fails to start container > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1373981/+subscriptions > -- 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/1373981 Title: ubuntu 14.10 server, amd64 - lxc-start fails to start container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1373981/+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
