Issues with logging in multiple docker images

[clonm]

Some are logging in the wrong place and others don't seem to be logging at all (log files in /srv/var/log are stale and there's nothing more recent in /var/log within the containers). I'm not sure exactly what the relationship is across runit/svlogd, rsyslogd, and the applications themselves/whatever they default to.

Is there likely to be an issue with runit and bionic in general? I know there's a [tozd/runit:ubuntu-bionic], but haven't had success googling runit + bionic. The closest thing I did find is a guide to setting it up on Xenial, and if I'm understanding it correctly (which I likely am not), I think it's saying it will be much harder or impossible in Bionic and all future Ubuntu releases?

Along the way, we also acknowledge that sysv-init scripts are broken for good in Xenial and will be completely gone in Yakkety Yak and further releases.
...

• in Yakkety Yak the initscripts package is no more built

(On a side note, you should probably be concerned about the last fact, as it means upstart+sysv will not work in Yakkety Yak anymore, leaving us to systemd alone for init system choices).

That said, it's not just the bionic-based sympa image that's having issues, but some of the trusty-based images as well (powerdns on server2 only, owncloud, and I think some of the ngnix-based containers although part of that is me still figuring out how all the different instances of nginx relate).