No colorized output

[yajo]

When using docker-compose logs, it adds colors by container, but if the container's logs were colorized, they appear all in the same color.

Colorized logs are very useful, so it should be respected by docker-compose.

[hadim]

I confirm the bug. docker run outputs the correct colorized logs if they exist.

[aanand]

Can you provide a minimal failing case? I've got logs producing correctly coloured output with a small docker-compose.yml:

test:
  image: ubuntu:14.04
  command: ['sh', '-c', 'echo \\033[31mhello; echo \\033[32mworld']

[hadim]

I don't remember what I did but I can't reproduce the bug anymore... I tried using forego which was the initial thing for what I needed colorized output, but I can't reproduce it anymore.

Wait for @yajo and see if it still se the bug before closing it maybe.

[yajo]

Weird, your test case works, but I'm using Odoo from yajo/odoo image and it does not show colors in docker-compose but does in plain docker. See:

docker-compose version
docker-compose version 1.5.2, build 7240ff3
docker-py version: 1.6.0
CPython version: 2.7.10
OpenSSL version: OpenSSL 1.0.1k-fips 8 Jan 2015

Is it possible that Odoo (Python) is doing anything to check the type of terminal and it gets different in docker-compose and docker?

[aanand]

Yes, very possible. Try adding tty: true to the service config.

[yajo]

Amazing, it works, thanks!

[Elindorath]

I don't think adding tty: true is a suitable solution since #3106 ...

[inquire]

The tty:true doesn't work anymore :(

[wiktor-obrebski]

confirm. this problem is back. @shin- maybe you can open this issue back?

[ikasty]

You can use 'cat' solution.

[wiktor-obrebski]

this is a diffrent problem, but I realized that my output color problem can be result of my app specific setup.

[mindscratch]

The tty: true works for me with docker-compose 1.9.0

[pmgouveia]

when I activated this... my docker-compose does not terminate anymore.. stays hanging...
#3106

[Cyral]

If you are using Node, a lot of packages use a coloring library like chalk which checks for certain things such as the --color flag or if it is a terminal to enable color support.

So just add --color when you start your app, in my case webpack didn't have color output:

"scripts": {
  "start": "./node_modules/.bin/webpack-dev-server --color",
},

[j0hnm4r5]

Adding both

tty: true

and

environment: 
    - TERM=xterm-256color`

dit it for me.

[IAMtheIAM]

Interesting, tty:truedid not work for docker-compose run service when reattaching with docker attach service_generated_name, but it does work for docker-compose up to retain color when reconnecting via docker-compose logs.

How do we get color when "attaching" to an existing docker container started by run and connected to output by docker attach?

[danvdumitriu]

A simple workaround which consists in starting docker-compose in the background, writing the output to a logfile and then tailing the logfile.

docker-compose up --build | tee /tmp/docker.log > /dev/null &
tail -f /tmp/docker.log | while IFS= read -r line; do printf '%b\n' "$line"; done

[cerinoligutom]

Adding tty: true worked for me.

Windows 10 Pro 64 bit

[bertho-zero]

This works for me without tty: true:

    environment:
      DEBUG_COLORS: "true"
      TERM: xterm-256color
      COLORTERM: truecolor