# Filebeat not reading all docker container logs

**URL:** https://discuss.elastic.co/t/filebeat-not-reading-all-docker-container-logs/160801
**Category:** Beats
**Tags:** filebeat
**Created:** [December 13, 2018, 6:51pm UTC](https://discuss.elastic.co/t/filebeat-not-reading-all-docker-container-logs/160801 "2018-12-13T18:51:09Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)
#### Post date: [December 20, 2018, 11:15pm UTC](https://discuss.elastic.co/t/filebeat-not-reading-all-docker-container-logs/160801/5 "2018-12-20T23:15:57Z")

</div>

With your configuration only logs written to `stdout` will be collected, maybe the services that are not being collected are logging to `stderr`. Try to remove the `stream: "stdout"` line, or change it to `stream: "all"`.

> In the logs there is an error:  
> ERROR log/harvester.go:281 Read line error: invalid CRI log format; File: /var/lib/docker/containers/[container id]-json.log

If you continue finding this error take a look to [this comment](https://discuss.elastic.co/t/filebeat-6-4-2-read-line-error-invalid-cri-log-format-file/154506/12).

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-not-reading-all-docker-container-logs/160801)._