[BUG] docker compose run --quiet-pull doesn't work #10714
Assignees
Labels
Comments
|
Hello @chris-dekker |
|
Thanks for the reply @glours ! so what is the way to avoid those service state logs altogether to only print the run command's output? |
|
This is the default output of the
|
|
How do I get just the latter? |
|
Did you try to do a |
|
While the OP seems to actually have a different problem, I do get the pull logs on gitlab even with compose version: docker: Im a missing something? |
|
I see the same thing as @leberknecht. The situation is a quite frustrating because in CI, while I can hide/ignore the pull step verbose output, because of this bug, I'm forced to have a run step containing the pull progress and the run output that I'm interested in. Or in other words, it seems way more valuable to have ( |
|
Hello! I am seeing the same as @leberknecht. Is there any update on this issue? Thanks! |
|
@uuf6429 As you can see everything is displayed as expected on my side with Compose |
|
As mentioned in the contributing guide, without any feedback to our last comment for a while I'm closing the issue |
|
@glours I can replicate the issue with docker compose v2.23.3 with GitHub Action runner (hosted by GitHub). Hopefully it's enough to reopen the issue. version: '3.8'
services:
mongo:
image: mongo:4.4.28@sha256:17330999a8d1e2f8d1805596c48a7dab5265d8da36ac4de20a5c35c32ea2d6b8
tmpfs: /data/db
command: --bind_ip localhost,mongo
my-container:
# omitThe command is: docker compose \
--file compose.test.yml \
run \
--rm \
--quiet-pull \
nexusHere is the output: The difference in running the command is the daemon. |
|
the |
|
@erickguan @leberknecht |
|
Hm, i checked again, i can confirm that |
|
@glours Thanks for checking! I can replicate the same in my terminal on a Macbook Pro. I am puzzled. The only difference was tty between GitHub Actions runner and my terminal. So progress is the core writer to the log. Then I did some digging in the code. But did When starting dependencies, it seems this flag is not passing to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Running
docker compose run --quiet-pull ..should avoid printing the container pulling information, but this simply doesn't work. It still prints the followingBefore printing the actual container's run command output.
This messes with scripts that use the run command's output which is now mixed with container pull information.
Was already reported and re-reported here, but that issue was closed without resolution.
Steps To Reproduce
docker compose run --quiet-pull wdio npm run wdioCompose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: