This is unrelated to docker, it's a bug in a minidlna patch that was added for Debian to possibly allow using logrotate for minidlna. However, according to a Debian bug report, the log-reopen on signal does not actually work due to a mistake in the patch, since the log-reopen function is not called on receiving the logrotate signal (SIGUSR1 or maybe SIGHUP, don't remember).
Since the patch can't handle logfilename=NULL (i.e. log to stdout), Debian and Ubuntu minidlna versions crash when using the -d option. I reported this to Debian some time ago: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=749265 ** Bug watch added: Debian Bug tracker #749265 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749265 ** Also affects: minidlna (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749265 Importance: Unknown Status: Unknown ** Summary changed: - Segfault running minidlna in 14.04 docker container + Segfault running "minidlnad -d" in 14.04 docker container -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363069 Title: Segfault running "minidlnad -d" in 14.04 docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/minidlna/+bug/1363069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
