[systemd-devel] SHM parameters on nspawn containers
Florian Koch
florian.koch1981 at gmail.com
Wed Aug 26 13:28:29 PDT 2015
Hi,
Ohne way is to use an More recent Kernel, with 3.16+ the Kernel defaults for These values where changed to unlimeted
Regards Florian
Von meinem iPhone gesendet
> Am 26.08.2015 um 17:34 schrieb Chris Bell <cwbell at narmos.org>:
>
> Hello all,
>
> I'm attempting to run GitLab (with postgresql) on a CentOS 7 container with systemd-nspawn. Postgre keeps failing, because it tries to allocate more shared memory than the container seems to allow. I cannot use sysctl to write the kernel.shmmax and kernel.shmall properties, since /sys isn't *real* (sysctl -w fails with 'read-only file system'). I have the values set correctly in the host machine, but they do not seem to propagate/be available to the container. Is there any way I can set (increase) the kernel.shmmax and kernel.shmall values in the container?
>
> Host: systemd 224 on Arch LTS Kernel (3.14.51)
> Guest: systemd 208 on CentOS 7 container
>
> Thanks,
>
> Chris
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
More information about the systemd-devel
mailing list