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 cwb...@narmos.org: Hello all, I'm attempting to run GitLab (with postgresql) on

[systemd-devel] systemd-nspawn network interface name collisions

2015-06-18 Thread Florian Koch
Hi, if i understnd this correct, the network interface names (veth and macvlan) are created with the frist 11 Caracters from the Containername (Machinename). Now if you use similar names for conatiners, like com.$company.$devision.$name1 com.$company.$devision.$name2

[systemd-devel] Fwd: systemd-nspawn network interface name collisions

2015-06-18 Thread Florian Koch
forgot the list -- Forwarded message -- From: Florian Koch florian.koch1...@gmail.com Date: 2015-06-18 22:03 GMT+02:00 Subject: Re: [systemd-devel] systemd-nspawn network interface name collisions To: Lennart Poettering lenn...@poettering.net 2015-06-18 18:42 GMT+02:00

Re: [systemd-devel] Nspawn / getty restart loop

2014-12-06 Thread Florian Koch
the container-getty@.service only needs to be present, not enabled, you can disable the unit, then the logs go away 2014-12-06 15:49 GMT+01:00 Meech meech...@gmail.com: Running Arch64 / Systemd 217. I have a barebones container initialized with pacstrap. The conatiner is stored in /var/lib