[lxc-users] BIND isn't recognizing container CPU limits

[Serge E. Hallyn]

Bind is probably looking at /sys/bus/cpu/drivers/processor/ ?

Quoting Joshua Schaeffer (jschaeffer0922 at gmail.com):
> I saw this in my log file when I start BIND9 and was a little concerned, since I limit the container to 2 CPU's and this is an unprivileged container:
> 
>     Aug  2 16:04:39 blldns01 named[320]: found 32 CPUs, using 32 worker threads
>     Aug  2 16:04:39 blldns01 named[320]: using 16 UDP listeners per interface
>     Aug  2 16:04:39 blldns01 named[320]: using up to 4096 sockets
> 
> >From the container:
> 
>     root at blldns01:~# cat /proc/cpuinfo | grep -c processor
>     2
> 
> >From the host:
> 
>     lxduser at blllxd01:~$ lxc config get blldns01 limits.cpu
>     2
> 
> Why would BIND be able to see all the cores of the host? I can certainly limit BIND to using less threads, but it shouldn't be able to see that many cores in the first place. I'm using LXD 2.15
> 
> Thanks,
> Joshua Schaeffer

> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users