[lxc-users] sysctl -p no longer allowed in container

[Fajar A. Nugraha]

On Fri, Dec 11, 2015 at 12:20 PM, Dan Kegel <dank at kegel.com> wrote:

> Came back to this because it hit me again (14.04 host, 15.10 guest this
> time).
> I actually don't need to be able to write to /proc/sys/kernel/sem
> from inside the container; I just need its limits to be high enough.
>
> $ uname -a
> Linux dank-desktop 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7
> 15:20:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> $ apt-cache policy lxc
> lxc:
>   Installed: 1.1.5-0ubuntu3~ubuntu14.04.1
>
> Looks like at one point, inside was going to inherit from outside:
> http://lists.linuxfoundation.org/pipermail/containers/2014-May/034544.html
> but that doesn't seem to be happening here:
>
> $ cat /proc/sys/kernel/sem
> 250 65536 32 32768
> $ sudo lxc-start -n foo
> $ ssh foo
> $ cat /proc/sys/kernel/sem
> 250 32000 32 128
>
>

Do you have lxcfs installed? At least my installation has high-enough limit
without me having to do anything.

dev ~ # cat /proc/sys/kernel/sem
32000   1024000000      500     32000
dev ~ # lxc-attach -n app01 -- cat /proc/sys/kernel/sem
32000   1024000000      500     32000

ubuntu 14.04, linux-image-generic-lts-wily 4.2.0.18.13,
lxc 1.1.5-0ubuntu3~ubuntu14.04.1 (from backports),
lxcfs 0.12-0ubuntu5~ubuntu14.04.1~ppa1 (from ppa).

-- 
Fajar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20151211/33027b21/attachment.html>