Quoting Rintcius Blok (rintc...@gmail.com):
> Hmm.. I just had the same problem again.
> I thought it was this bug:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021471
> (fixed in 3.5.0-17.28)
>
> Am I having the correct version installed? :
> 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19
Hmm.. I just had the same problem again.
I thought it was this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021471
(fixed in 3.5.0-17.28)
Am I having the correct version installed? :
3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
If I n
Ok thanks! I saw those messages in syslog indeed, so could very well be
that issue for me as well.
I have just upgraded. Will let you know if this solves the problem.
Rintcius
On 19/11/12 14:37, Serge Hallyn wrote:
> Since you say that after this you cannot start any containers at all until
> a
Since you say that after this you cannot start any containers at all until
a host reboot, I think what you get is a known kernel netdev refcounting
bug. (Check your host syslog messages.) You might try a backported raring
kernel.
-serge
Quoting Rintcius Blok (rintc...@gmail.com):
> Hi,
>
> I g