Idk how many people care, but one of the new features in 0.27 is the addition of ContainerLoggers, and a logger that uses logrotate. Here's a blog post I wrote on how to get you started with getting this working: http://continuousfailure.com/post/mesos27_logging/
> would capture std{out,err} indefinitely, which could cause the slave host to run out of disk space
That sounds to me like something everyone would care about. I have started setting Docker's log-opt to max-size=128m and max-file=3 expressly to side-step that kind of nonsense. It's a great happy medium between "logs go out over the network", which impedes one's ability to use "docker log" for quick-and-dirty viewing, but not blowing out the disks. We've enjoyed great success with logspout, since it captures every container, relieving us of the need to configure them individually.
That sounds to me like something everyone would care about. I have started setting Docker's log-opt to max-size=128m and max-file=3 expressly to side-step that kind of nonsense. It's a great happy medium between "logs go out over the network", which impedes one's ability to use "docker log" for quick-and-dirty viewing, but not blowing out the disks. We've enjoyed great success with logspout, since it captures every container, relieving us of the need to configure them individually.