Shulou(Shulou.com)06/02 Report--

This article introduces the knowledge of "how to solve the space problem caused by too large kubernetes Pod log". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

When log-driver is json-file, the container log is stored under / var/lib/docker/containers/ and is stored as a container_id-json.log file.

But by default, log-driver is set to journald and handed over to the system's journal service for management

Log restrictions can be done through docker option, but first change log-driver to json-file mode

# cat / etc/sysconfig/docker OPTIONS='--log-driver=json-file-log-opt max-size=50m-log-opt max-file=5'

Clear the log through

# cat / dev/null > / var/lib/docker/containers/CONTAINER_ID/CONTAINER_ID-json.logOR# cat / dev/null > $(docker inspect-- format=' {{.LogPath}} 'CONTAINER_ID) "how to solve the space problem caused by too large kubernetes Pod logs" ends here. Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.