search

docker / compose

Define and run multi-container applications with Docker
https://docs.docker.com/compose/
Apache License 2.0
33.98k stars 5.22k forks source link

[BUG] Building images not visible in progress events, *except* in dry-run mode #11403

Open felixfontein opened 9 months ago

felixfontein commented 9 months ago

Description

When running docker compose --progress plain up --dry-run --detach, you can see build events:

 DRY-RUN MODE -    build service foobar 
 DRY-RUN MODE -  ==> ==> writing image dryRun-8843d7f92416211de9ebb963ff4ce28125932878 
 DRY-RUN MODE -  ==> ==> naming to my-python 
 DRY-RUN MODE -  Network compose_default  Creating
 DRY-RUN MODE -  Network compose_default  Created
 DRY-RUN MODE -  Container compose-foobar-2  Creating
 DRY-RUN MODE -  Container compose-foobar-1  Creating
 DRY-RUN MODE -  Container compose-foobar-2  Created
 DRY-RUN MODE -  Container compose-foobar-1  Created
 DRY-RUN MODE -  Container ompose-foobar-2  Starting
 DRY-RUN MODE -  Container ompose-foobar-2  Started
 DRY-RUN MODE -  Container ompose-foobar-1  Starting
 DRY-RUN MODE -  Container ompose-foobar-1  Started

(The missing c is #11402.)

If you run the same without --dry-run, you don't:

 Network compose_default  Creating
 Network compose_default  Created
 Container compose-foobar-2  Creating
 Container compose-foobar-1  Creating
 Container compose-foobar-1  Created
 Container compose-foobar-2  Created
 Container compose-foobar-1  Starting
 Container compose-foobar-1  Started
 Container compose-foobar-2  Starting
 Container compose-foobar-2  Started

Steps To Reproduce

See description.

Compose Version

No response

Docker Environment

No response

Anything else?

No response

felixfontein commented 9 months ago

(The above are the stderr output only. On stdout you can see that something was built if not in dry-run mode, but that output is even more unstructured.)

felixfontein commented 8 months ago

11498 fixes this.

github-actions[bot] commented 3 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

felixfontein commented 3 months ago

Well, there is a PR for this issue, which has been sitting around unreviewed since February 13th. I don't think it makes sense to close it yet.

stale[bot] commented 3 months ago

This issue has been automatically marked as not stale anymore due to the recent activity.