<div dir="ltr">Found it - <a href="https://github.com/lxc/lxd/blob/master/doc/production-setup.md">https://github.com/lxc/lxd/blob/master/doc/production-setup.md</a></div><div class="gmail_extra"><br><div class="gmail_quote">On 21 July 2017 at 15:44, Ivan Kurnosov <span dir="ltr"><<a href="mailto:zerkms@zerkms.ru" target="_blank">zerkms@zerkms.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I have a very strange situation and I'm not even sure if it's the right mail list to post, but let's see.</div><div><br></div><div>I have successfully reproduced it on 2 machines: on a real hardware and in virtualbox vm.</div><div><br></div><div>Given, the host OS Ubuntu 16.04.2 (will all updates), I'm creating a bunch of containers. To reproduce the problem I'm using the following script:</div><div><br></div><div><div>lxc launch ubuntu:16.04 container-1</div><div>sleep 5</div><div>lxc exec container-1 ps ax</div><div><br></div><div>lxc launch ubuntu:16.04 container-2</div><div>sleep 5</div><div>lxc exec container-2 ps ax</div><div><br></div><div>lxc launch ubuntu:16.04 container-3</div><div>sleep 5</div><div>lxc exec container-3 ps ax</div></div><div>....</div><div><br></div><div>etc up to container-30.</div><div><br></div><div>At some point (different on both machines, but consistent) the container is created, started but has /sbin/init as it ONLY running process. So no systemd or any other system daemon running there apart of /sbin/init. And after that point every other container I create looks broken in the very same way.</div><div><br></div><div>Here is how the output from the script above looks on the edge between "proper containers" and "broken containers":</div><div><br></div><div><div>Creating container-12</div><div>Starting container-12</div><div> PID TTY STAT TIME COMMAND</div><div> 1 ? Ss 0:00 /sbin/init</div><div> 53 ? Ss 0:00 /lib/systemd/systemd-udevd</div><div> 57 ? Ss 0:00 /lib/systemd/systemd-journald</div><div> 236 ? Ss 0:00 /sbin/dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.<wbr>leases -I -df /var/lib/dhcp/dhclient6.eth0.<wbr>leases eth0</div><div> 292 ? Rs 0:00 /usr/bin/python3 /usr/bin/cloud-init init</div><div> 295 ? S 0:00 /bin/sh -c tee -a /var/log/cloud-init-output.log</div><div> 296 ? S 0:00 tee -a /var/log/cloud-init-output.log</div><div> 300 ? Rs+ 0:00 ps ax</div><div>Creating container-13</div><div>Starting container-13</div><div> PID TTY STAT TIME COMMAND</div><div> 1 ? Ss 0:00 /sbin/init</div><div> 221 ? Rs+ 0:00 ps ax</div></div><div><br></div><div>All the containers after container-13 are created "broken". If I create another container now - it also would not start properly.</div><div><br></div><div>But if I only leave 11 containers running and create another one or restart one of "broken" ones - then it would start fine.</div><div><br></div><div>It only is reproducible with ubuntu 16.04 containers, 17.04 run fine (at least up to 30 simultaneously running containers).</div><div><br></div><div>The number of containers the OS "allows" to run properly is different on both of machines I tried (12 on the real hardware, and 20 in the virtualbox vm).</div><div>There is plenty of memory available, so memory is not a problem.</div><div><br></div><div>There is nothing particularly interesting in the host machine's syslog or lxd.log.</div><div><br></div><div>And in the container there are no logs to read actually, since journalctl and rsyslog weren't even started.</div><div><br></div><div><br></div><div>Any suggestions on where I could dig further?</div><span class="HOEnZb"><font color="#888888"><div><div><br></div>-- <br><div class="m_7607340492216222683gmail_signature">With best regards, Ivan Kurnosov</div>
</div></font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">With best regards, Ivan Kurnosov</div>
</div>