[Lxc-users] Many containers and too many open files

Daniel Lezcano daniel.lezcano at free.fr
Mon Feb 28 10:22:18 UTC 2011


On 02/28/2011 01:55 AM, Trent W. Buck wrote:
> Daniel Lezcano<daniel.lezcano at free.fr>  writes:
>
>> I was using dnsmasq as a dns and a dhcp server and sending the
>> hostname as an identifier for the dhcp protocol, so I was able to
>> reach the container without taking care of the ip address / mac
>> address. But I noticed dnsmasq was collapsing and taking a very long
>> time before sending an ip address after ~ 600 containers.
> This interests me: do you attribute it to scalability issues in dnsmasq?
> I use it heavily in /24 networks (i.e.<254 hosts), and it'd be good to
> know in advance if it won't handle a /16 network.

It handles this number of containers but when the number reach ~600 
containers it seems to collapse.
I didn't investigate more, maybe the problem is not coming from dnsmasq 
but from the routing cache table overflow.

I am waiting some feedbacks from Andre with the kernel boot option. So 
he should say if he is facing the same problem with dnsmasq or not.




More information about the lxc-users mailing list