Re: [systemd-devel] SHM parameters on nspawn containers

2015-08-28 Thread Chris Bell
On 2015-08-26 20:28, Florian Koch wrote: Ohne way is to use an More recent Kernel, with 3.16+ the Kernel defaults for These values where changed to unlimeted This worked. I booted the host with a 4.1 kernel, and the values were appropriately high. Thanks! On 2015-08-27 18:18, Lennart Poette

Re: [systemd-devel] SHM parameters on nspawn containers

2015-08-27 Thread Lennart Poettering
On Wed, 26.08.15 11:34, Chris Bell ([email protected]) wrote: > 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 sys

Re: [systemd-devel] SHM parameters on nspawn containers

2015-08-26 Thread Florian Koch
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 : > > Hello all, > > I'm attempting to run GitLab (with postgresql) on a CentOS 7 c

[systemd-devel] SHM parameters on nspawn containers

2015-08-26 Thread Chris Bell
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 /