Doug Szumski bd54b99132 Constrain the size of Docker logs ... Even though Kolla services are configured to log output to file rather than stdout, some stdout still occurs when for example the container re(starts). Since the Docker logs are not constrained in size, they can fill up the docker volumes drive and bring down the host. One example of when this is particularly problematic is when Fluentd cannot parse a log message. The warning output is written to the Docker log and in production we have seen it eat 100GB of disk space in less than a day. We could configure Fluentd not to do this, but the problem may still occur via another mechanism. Change-Id: Ia6d3935263a5909c71750b34eb69e72e6e558b7a Closes-Bug: #1794249		2018-10-11 13:31:47 +01:00
..
docker_apt_repo.j2	Change the docker daemon name in Debian 9 on Arm	2018-01-09 15:02:40 +08:00
docker_systemd_service.j2	Constrain the size of Docker logs	2018-10-11 13:31:47 +01:00
docker_yum_repo.j2	Unify global syntax in baremetal role	2017-09-19 11:23:20 +02:00