Azure service container logs need to be rotated about for-azure HOT 5 OPEN

@pekajota you can access host file system using something like the following:
docker run --rm -it --privileged --pid=host justincormack/nsenter1 /bin/ash

You may want to check if the waagent's log files are taking up a lot of space. We fixes a log rotation issue with the log file recently. Which version are you on?

from for-azure.

Hi @ddebroy, thanks for the info. I can now access the host.

I've just found out that the source of 16GB worth of logs is docker4x/l4controller-azure:17.06.0-ce-azure2. It is printing out logs in debug mode. Do you know what might have caused this?

from for-azure.

@ddebroy I just found out that dockerd runs with debug enabled by default:

dockerd --pidfile=/run/docker.pid -H unix:///var/run/docker.sock --debug --storage-driver overlay2

Is this an expected behavior?

from for-azure.

@pekajota thanks for reporting this issue. It seems the l4controller container log (generated by the l4controller that keeps the Azure load balancer and Swarm ports in sync) is not being rotated. We will enable this and is a bug in our init logic.

from for-azure.

Changed title to reflect the issue

from for-azure.