[based on email thread and partially copy/pasting from the reply by Tim Rozet]
Description of problem:
The OpenDaylight container currently logs to 2 places: karaf.log (which is mounted to somewhere outside of the container) and STDOUT (which the Docker container runtime feeds into journald; to access logs with ODL you can either do "docker logs opendaylight-api" OR you can use journalctl like "journalctl CONTAINER_NAME=opendaylight-api").
This double logging is at best slightly confusing for end-users, and at worst not ideal for performance.
TripleO services are moving to use docker logging based on stdout. ODL is one of the first services to do this. Other services mount their logs into /var/log/containers/ on the host.
From OSPD perspective, we only want 1 way for customers to access logging, this will be using docker logging and not karaf.log inside the container.
ODL logging is in BÒTH karaf.log* file(s) AND "docker logs opendaylight-api" (= "journalctl CONTAINER_NAME=opendaylight-api").
The karaf.log only contains a few ODL start up log messages, and nothing after that; all other ongoing logging goes only to STDOUT = "docker logs opendaylight-api" = "journalctl CONTAINER_NAME=opendaylight-api".
The confusion in Bug 1559055 re. journald rotation should be cleared up BEFORE we make this change.
This change should affect only ODL in the container, not for the base RPM.
The way to technically do this has already been discussed in https://bugzilla.redhat.com/show_bug.cgi?id=1559055#c21 (which was technically about something else) :
Comment out "log4j2.rootLogger.appenderRef.RollingFile.ref = RollingFile" in /opt/opendaylight/etc/org.ops4j.pax.logging.cfg.
Closing this as won't fix because docker is being replaced by Podman starting OSP15.