Jason Greathouse

Looks like this is an undocumented "feature" of streaming the docker logs api. Docker is putting a 8 byte header on the front of each docker line. The header gets...

First :-1: on https://hub.docker.com/r/bekt/logspout-logstash not tagging releases. There are 2 checks in there already. 1.) Has the container set TTY=false If the container has TTY set to true the log...

@je-al I'm scratching my head on this. We are running almost the same version, api 1.30/17.06.0-ce. Can you run logspout with DEBUG=true environment var? I'm curious what api version/TTY is...

@je-al you don't happen to have a filter in your logstash pipeline that is dropping the "unicode garbage" from the beginning of the message? So we are now "fixing" the...

I'm out of ideas. I can't think of a reason why your setup would be different. I'll think on a better way to detect if the headers are on the...

@je-al I think I figured it out. Its the ALLOW_TTY option the difference between our setups. When ALLOW_TTY true is set, logspout is setting the RawTerminal option on the docker.client.Logs()...

@je-al can you try out this fix :arrow_up: I have a container built with the logstash plugin here: jgreat/logspout:logstash.smarter-fix-log-header-bytes.1

I'm running into this too. I pretty regularly have a successful `terraform apply` (everything shows successful and complete) and end up with `helm_release` resources that show `~ status = "failed"...

I can't speak for everyone, but we haven't seen this issue in a while.

Can we get a bump on this issue, its pretty critical. I just destroyed my laptop thanks to this bug.