# Filebeat docker input: Error getting container info: \<nil\>

**URL:** https://discuss.elastic.co/t/filebeat-docker-input-error-getting-container-info-nil/153878
**Category:** Beats
**Tags:** filebeat
**Created:** [October 24, 2018, 9:56pm UTC](https://discuss.elastic.co/t/filebeat-docker-input-error-getting-container-info-nil/153878 "2018-10-24T21:56:12Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![justinw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justinw/32/40277_2.png) [@justinw](https://discuss.elastic.co/u/justinw)
#### Post date: [October 24, 2018, 9:56pm UTC](https://discuss.elastic.co/t/filebeat-docker-input-error-getting-container-info-nil/153878/1 "2018-10-24T21:56:12Z")

</div>

Hi,

Running filebeat 6.3.2 with "- add\_docker\_metadata" set, and periodically see this in the logs:

ERROR docker/watcher.go:233 Error getting container info: \<nil\>

Can you please provide some information as to what may be causing this?

Thanks, Justin

---

<div class="post-metadata">

### Author: ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)
#### Post date: [October 25, 2018, 1:27pm UTC](https://discuss.elastic.co/t/filebeat-docker-input-error-getting-container-info-nil/153878/2 "2018-10-25T13:27:33Z")

</div>

From looking at the code and your error trace:

> <https://github.com/elastic/beats/blob/99824df163863478d27688206e18ec27bc1b3ac5/libbeat/common/docker/watcher.go#L247-L253>

It appears we make an API call and don't receive any containers information.

how often you see this in your log?

---

<div class="post-metadata">

### Author: ![justinw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justinw/32/40277_2.png) [@justinw](https://discuss.elastic.co/u/justinw)
#### Post date: [October 25, 2018, 5:55pm UTC](https://discuss.elastic.co/t/filebeat-docker-input-error-getting-container-info-nil/153878/3 "2018-10-25T17:55:22Z")

</div>

Not super often, but often enough that I felt it was worth asking about.

Looking at that loop, it seems like the only way to get there is after a 'start' or 'update' event. Is it potentially a timing issue / race condition if the watcher got an event for a start or update but cannot find the container by id?

Best, Justin

---

<div class="post-metadata">

### Author: ![justinw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justinw/32/40277_2.png) [@justinw](https://discuss.elastic.co/u/justinw)
#### Post date: [October 25, 2018, 9:20pm UTC](https://discuss.elastic.co/t/filebeat-docker-input-error-getting-container-info-nil/153878/4 "2018-10-25T21:20:37Z")

</div>

I also see this one, a little more frequently

2018-10-25T20:46:10.588Z ERROR kubernetes/watcher.go:254 kubernetes: Watching API error EOF

Looks like that comes from either of these two places:

> <https://github.com/elastic/beats/blob/master/libbeat/common/kubernetes/watcher.go#L244>

  

> <https://github.com/elastic/beats/blob/master/libbeat/common/kubernetes/watcher.go#L254>

Is this something to be concerned about?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 22, 2018, 9:20pm UTC](https://discuss.elastic.co/t/filebeat-docker-input-error-getting-container-info-nil/153878/5 "2018-11-22T21:20:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.