4 ms·
It's crazy that (until now) docker always logged stdout/stderr to a file, and never rolled it. Without a separately configured logrotate (in copy-truncate mode)
by ploxiln 12y ago
It's crazy that (until now) docker always logged stdout/stderr to a file, and never rolled it. Without a separately configured logrotate (in copy-truncate mode), these log files will grow without bound, until the container is removed (usually replaced).
- bsrx 12y agoIt may be critically important, but they can't do everything at once. They're moving incredibly fast as it is. Other people were attempting to solve this problem too - https://registry.hub.docker.com/u/kiyoto/docker-fluentd/ https://registry.hub.docker.com/u/kiyoto/docker-fluentd/
- amouat 12y agoReminds me of the day I foolishly did "docker run -d debian yes" so I could play with some of the inspection commands. I forgot about it and an hour later it had eaten nearly all of my hard disk space...