Conversation
ndeloof
left a comment
There was a problem hiding this comment.
I don't think we need a new --log flag, which would only apply in combination with --wait. We can just attach to containers when --wait is set; users who prefer to keep it quiet can redirect output, rely on start --wait or maybe use --attach=.
Doing so you don't need a new flag not new AP attributes, the challenge becomes getting composeService.up to stop early, after container all get healthy (which is managed in start
okay noted, will work on it. |
Signed-off-by: Mark Jagyo <[email protected]>
Signed-off-by: Mark Jagyo <[email protected]>
79e9a75 to
bd9a238
Compare
Signed-off-by: Mark Jagyo <[email protected]>
bd9a238 to
d96fb10
Compare
|
@ndeloof I think its working now on |
Signed-off-by: Mark Jagyo <[email protected]>
Signed-off-by: Mark Jagyo <[email protected]>
7006558 to
5da16ce
Compare
Signed-off-by: Mark Jagyo <[email protected]>
5da16ce to
1be89db
Compare
Introduce a --log flag for docker compose wait and docker compose up --wait to emit progress output while services are starting.