Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
felixfontein opened this issue Jan 24, 2024 · 2 comments · May be fixed by #11498
Open

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

felixfontein opened this issue Jan 24, 2024 · 2 comments · May be fixed by #11498

Comments

@felixfontein
Copy link
Contributor

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
Copy link
Contributor Author

(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 felixfontein linked a pull request Feb 13, 2024 that will close this issue
@felixfontein
Copy link
Contributor Author

#11498 fixes this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant