Compose: Old logs dumped to terminal on startup
Each time I use docker-compose up to restart an existing set of containers, I see huge amounts of old log messages dumped to the screen.
This was not the case before 1.4.0. Older versions did only output new messages.
I don't need this and suggest a feature to turn that off (unless there already is one, which I couldn't find).
mikehaertl
All 8 comments
This is a duplicate of #1756
You can docker-compose rm the containers if you want to remove the logs
dnephin
on 30 Sep 2015
But I don't want to rm existing containers. For example during development I have a MySQL container and don't want to loose the DB content on each startup. But will continue discussion in the other issue then.
mikehaertl
on 30 Sep 2015
Yes, sorry, I was just suggesting that as a possible workaround for now. We still need to fix the issue.
dnephin
on 30 Sep 2015
Any update on this. It's been 2 years.
hixus
on 28 Nov 2017
@dnephin any progress on fixing the issue?
coreylenertz
on 18 Dec 2017
Bump
Vivalldi
on 23 Apr 2018
I'm running into the same issue. docker-compose up is suddenly dumping one week worth of old logs, where previous invocations of docker-compose up didn't do that.
michaelfranzl
on 3 Jan 2019
Same here... Issue https://github.com/docker/compose/issues/1083 seems to hold more usable info. It is also closed.
kuzyn
on 2 Mar 2019
Related issues
darkrasid
路
3Comments
squeaky-pl
路
3Comments
maltefiala
路
3Comments
saulshanabrook
路
3Comments
dazorni
路
3Comments
Most helpful comment
I'm running into the same issue.
docker-compose upis suddenly dumping one week worth of old logs, where previous invocations ofdocker-compose updidn't do that.