Djordje Lukic fcddb77b48 Give progress its own context ...

The build and progress can't share the same context, the progress context
needs to live longer for the progress to be able to read all the messages
from build.

Signed-off-by: Djordje Lukic <djordje.lukic@docker.com>

2020-12-04 13:05:26 +01:00

..

e2e

split Up into Create+Start so logs don't collide with progress

2020-12-04 08:16:50 +01:00

backend.go

composeService to rely on apiClient

2020-11-27 10:21:36 +01:00

build.go

Give progress its own context

2020-12-04 13:05:26 +01:00

compose_test.go

compose ps implementation

2020-11-19 13:34:43 +01:00

compose.go

split Up into Create+Start so logs don't collide with progress

2020-12-04 08:16:50 +01:00

container.go

split Up into Create+Start so logs don't collide with progress

2020-12-04 08:16:50 +01:00

containers.go

split Up into Create+Start so logs don't collide with progress

2020-12-04 08:16:50 +01:00

convergence.go

attach to log stream by default on up

2020-12-03 16:51:00 +01:00

convert_test.go

backend.local: Refactor conversion code

2020-11-04 09:54:29 +01:00

convert.go

Ensure extensions map is not nil (should be set by compose-go)

2020-11-19 13:10:55 +01:00

dependencies_test.go

Add order to down command

2020-12-02 13:51:11 +01:00

dependencies.go

Fix service initial status in graph, in order to fix compose down duplicate removal of container (example : awesome-compose ELK stack)

2020-12-03 15:27:35 +01:00

doc.go

Update copyright

2020-09-22 12:13:00 +02:00

labels.go

split Up into Create+Start so logs don't collide with progress

2020-12-04 08:16:50 +01:00

util.go

apply linter recommendations

2020-11-19 17:35:34 +01:00

volumes.go

backend.local: Add rudimentary volume support

2020-11-04 09:54:29 +01:00