Winston colors don't work with docker

[molszanski]

If you run winston in container (in my case boot2docker OSX), colors get lost.
This doesn't happen with debug npm library e.g.

[indexzero]

I believe it is because it is not a tty.

[molszanski]

One can run a container with a -t -> Allocate a *pseudo*-TTY. That may be the issue.

[tarwich]

Having the same frustration running with forever.

# -c Allows me to monitor the logs in terminal, rather than having Forever move them to a file.
forever -vw -c node test.js

Output is not a TTY and this disables the color. I'd like the option to overrule this behavior, but I'm not sure if Winston is the one breaking this, or if it's something directly related to the console.

Also, piping into less -R doesn't show the colors, though I feel it should.

[tarwich]

...and fixed

passing --color=always to my program fixes this issue. The issue is not with Winston, but with Marak/colors.

That being said, Winston could enable the option with

var colors = require("colors");
if(somethingSaysIShouldColor)
    colors.enabled = true;

If I write a program and manually set require("colors").enabled = true, then it enables the colors for my (non-TTY) program, but not for included programs like Winston.

enabled option found here

[amitport]

thanks @tarwich
👍

[indexzero]

Fixed in #751. Released in winston@2.1.1