I tried doing that, but it didn't work.
ubuntu-bug lxc
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.............................
*** Problem in lxc
The problem cannot be reported:
This is not an official Ubuntu package. Please remove any third party
package and try again.
Press any key to continue...
All my machines are using the PPA at https://launchpad.net/~ubuntu-lxc/,
which apparently is unable to accept bugs filed this way.
On Mon, Aug 12, 2013 at 6:10 AM, Serge Hallyn <serge.hal...@ubuntu.com>wrote:
> Quoting Jay Taylor (j...@jaytaylor.com):
> > After further investigation yesterday, I am not convinced it is an
> > IP-address issue. The affected host machines are unable to start any
> > existing or newly created containers. The incident that triggered the
> > issue was cloning 1 container into 10 new ones, and then launching them
> all
> > simultaneously. Are there any known concurrency issues with LXC which
> > would explain why executing a lot of clone/start LXC commands at the same
> > time causes all of LXC to be rendered useless until the host machine is
> > physically rebooted?
>
> Assuming you're on a pretty stock ubuntu host, it would be helpful if
> you could file a bug with launchpad. Start one of the containers which
> fails, then do
>
> ubuntu-bug lxc
>
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
