This message was deleted.

Cannot answer your question directly but in our case we deployed a daemonset that runs a cron periodically.

truncate -s 0 /home/dockerlogs/*/*-json.log

+ a mount to

/var/lib/docker/containers:/home/dockerlogs/

Could also be a cronjob deployment.

Docker handles all the logging unlike something like containerd so you should configure it in the daemon.json like shown in this article: https://signoz.io/blog/docker-log-rotation/#configuring-docker-log-rotation Instead of doing it manually on all the nodes I personally would use config management tooling like Ansible or Salt to change it and keep it uniform on the nodes.

Thanks @white-park-86714, It’s a good option. Thanks @bulky-sunset-52084, but when you send a request to add a node from rancher UI, it just creates a node from your provisioner and then installs docker and RKE on it, I’m not sure you can set docker daemon config on each node of the cluster at the bootstrap time using Ansible. Unless you add node from Ansible config(I don’t know rancher allow us add node to downstream clusters from Ansible or not), in that case I’m not sure it can let us set docker daemon config from Ansible or not!