kytos-sdx containers keep restarting

[sajith]

Forking an issue off atlanticwave-sdx/sdx-docs#29. On my setup (Debian 12.7 on x86_64, Docker 27.2.1), kytos-sdx containers keep restarting.

$ docker logs amlight
Starting enhanced syslogd: rsyslogdrsyslog startup failure, child did not respond within startup timeout (60 seconds)
 already started.
/etc/openvswitch/conf.db does not exist ... (warning).
Creating empty database /etc/openvswitch/conf.db.
Starting ovsdb-server.
Configuring Open vSwitch system IDs.
Starting ovs-vswitchd.
Enabling remote OVSDB managers.
Starting Kytos controller in a tmux session: done
tail: cannot open '/var/log/syslog' for reading: No such file or directory
tail: no files remaining

The above log messages keep repeating as the containers keep restarting every minute. When these lines are commented out, the containers keep running:

sdx-continuous-development/data-plane/docker-compose.yml

Line 29 in 8b3d43f

command: tail -f /var/log/syslog

sdx-continuous-development/data-plane/docker-compose.yml

Line 57 in 8b3d43f

command: tail -f /var/log/syslog

sdx-continuous-development/data-plane/docker-compose.yml

Line 85 in 8b3d43f

command: tail -f /var/log/syslog

But I guess the real problem with rsyslogd still remains. I came across a Stack Overflow question about this:

https://stackoverflow.com/questions/35715720/rsyslog-inside-docker-containers-rsyslogd-is-not-running-failed

[sajith]

The likely cause is a rsyslogd bug triggered by a very high number of open file descriptors: rsyslog/rsyslog#5158

We can try either using a base image that has a newer rsyslogd, or use a workaround: https://gist.github.com/vicenterusso/ae6d6c903b790e5dae91c339c1ce2ba8