-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Closed
Description
This epic covers a bunch of improvements we'd like to make to the logs command.
default to not following (similar toin 1.7.0docker logs) (docker-compose logsbehavior is different fromdocker logs#2187, Flush log buffer when printing logs #1549)supportin 1.7.0-f, --follow(the current behaviour) to keep following log outputsupportin 1.7.0--tail=<num>to only show a number of lines from the end of the log (Feature: Ability to clear log history #1083, limit fig log #265)in 1.7.0-t, --timestampto add timestamps to the logs (Improvements todocker-compose logs#2227 (comment))if a new container is started whilein 1.7.0logsis running, logs for that container should start to show up in the log stream (''docker-compose logs'' does not show logs for new containers #1115)if the log stream is done (the containers have stopped) logs should exit (logs doesn't exit if the container is already stopped #1866)in 1.7.0flush the buffer more frequently to deal with buffered output (container logs are missing whenFixed in 1.5.1fig upby Webstorm #1060, Flush log buffer when printing logs #1549)- continue printing logs after the first SIGINT until all containers exit (or we get another SIGINT) (Continue printing log output after Ctrl-C has been pressed #592)
--jsonoutput the raw json lines (json-file logs are not valid JSON #2156)
logs doesn't exit if the container is already stopped #1866 includes a proposal for how to support many of these features
simonvanderveldt and evandrocoan
Metadata
Metadata
Assignees
Labels
No labels