Description of problem: Containers that generate a lot of docker logs can result in filling up the disk containing docker's logs. Currently there is no management of the docker logs generated by containers. The installer should configure docker logging to manage log files. There are a couple of options I see: 1) Configure docker's log rotation functionality 2) Configure docker to log to systemd I believe 2 is how this problem is handled in atomic. Version-Release number of selected component (if applicable): 3.2.0 How reproducible: 100% Steps to Reproduce: 1. Run a container that generates a lot of docker logs 2. Wait 3. Actual results: Expected results: Additional info:
There is an issue when we try to configure the docker logging driver to use the journal logging, where fluentd will no longer collect and forward the logging data.
one of the problems is that the https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/blob/master/lib/fluent/plugin/filter_kubernetes_metadata.rb was designed specifically to work with the fluentd in_tail plugin with JSON formatted files in /var/log/containers/*.log. I'm currently working on allowing this plugin to work with the fluentd in_journal record format.
PR https://github.com/openshift/openshift-ansible/pull/1976
Check on openshift-ansible-3.2.1-1.git.0.b8d1b5e Install env with default configuration Check the docker option after installation OPTIONS=' --selinux-enabled --insecure-registry=172.31.0.0/16 --log-driver=json-file --log-opt max-size=50m' the default docker log option take effect, move this issue to VERIFIED.
Add more test result based on comment 10, when user specifying 'openshift_docker_options="-l warn --ipv6=false"', the default docker option - '--log-driver=json-file --log-opt max-size=50m' will be overwritten like the following: OPTIONS=' --selinux-enabled --insecure-registry=172.30.0.0/16 -l warn --ipv6=false'
*** Bug 1342544 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1344