Compose: Output to stdout?

[AlexKovalevych]

I use a build tool called bldr.io, it runs and prints output of each job, but for some reason it doesn't print any output from the docker-compose commands. The question is, does docker-compose actually print to stdout? E.g.:

docker-compose run   data "bin/phpunit -c app"
PHPUnit 4.8.9 by Sebastian Bergmann and contributors.

.............................................................

Time: 2.08 seconds, Memory: 24.50Mb

OK (61 tests, 183 assertions)

which works fine, but absolutely no output running the same command within the bldr.io:

 Using the 'test' profile
  - Run tests -



Running the tests job > Run tests

    [exec] - Starting

==============================

  RUN  'docker-compose' 'run' 'data' 'bin/phpunit -c app'

  RES  'docker-compose' 'run' 'data' 'bin/phpunit -c app'

==============================


  Build Success!

The non-compose commands prints output without any problems which makes me think docker-compose is different here.

[ilyakatz]

Curious about this too

[dnephin]

It might be an issue with buffering. There have been some issues in the past with jenkins.

You might want to try the -T option with run.

[dnephin]

docker-compose prints informational messages to stderr, and container output to the same stream as it was written to in the container (stdout or stderr).

No response from OP about trying -T, so going to close this issue.

[renevall]

Just to comment, I was trying to caught the output from the docker-compose up command in golang. As the OP, I wasn't getting any output. In the end I was suppose to caught the stderr output not the stdout output.

[steinybot]

@dnephin Why does docker-compose print informational messages to stderr? Is there a way to disable this and have it print to stdout instead?

[dnephin]

This issue is closed and very old. Please open a new issue if there is a specific message that you believe is going to the wrong stream.