# Filebeat: Error watching for docker events: context deadline exceeded

**URL:** https://discuss.elastic.co/t/filebeat-error-watching-for-docker-events-context-deadline-exceeded/211113
**Category:** Beats
**Tags:** docker, filebeat
**Created:** [December 9, 2019, 1:09pm UTC](https://discuss.elastic.co/t/filebeat-error-watching-for-docker-events-context-deadline-exceeded/211113 "2019-12-09T13:09:23Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![speechkey](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@speechkey](https://discuss.elastic.co/u/speechkey)
#### Post date: [December 9, 2019, 1:09pm UTC](https://discuss.elastic.co/t/filebeat-error-watching-for-docker-events-context-deadline-exceeded/211113/1 "2019-12-09T13:09:23Z")

</div>

Hi folks,

I have **filebeat 7.5.0 with autodiscovery** feature running **in a docker container** on a bunch of hosts. It logs **every 30-60 min** following error:

```
{
  "stream": "stderr",
  "caller": "docker/watcher.go:303",
  "level": "error",
  "message": "Error watching for docker events: context deadline exceeded"
}

```

With 7.4.2 a had the same issue. I couldn't really discover any issues correlated with the error — looks like it stays fully functional.

---

<div class="post-metadata">

### Author: ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)
#### Post date: [December 9, 2019, 3:09pm UTC](https://discuss.elastic.co/t/filebeat-error-watching-for-docker-events-context-deadline-exceeded/211113/2 "2019-12-09T15:09:47Z")

</div>

Hi @speechkey!

Thank you for reporting this!  
Most probably Docker API takes too long to respond for events at the point of reaching timeout.  
We will look into this! Maybe this should not be reported as an error to avoid confusion.

Thanks!

---

<div class="post-metadata">

### Author: ![speechkey](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@speechkey](https://discuss.elastic.co/u/speechkey)
#### Post date: [December 9, 2019, 4:17pm UTC](https://discuss.elastic.co/t/filebeat-error-watching-for-docker-events-context-deadline-exceeded/211113/3 "2019-12-09T16:17:23Z")

</div>

Hi @ChrsMark, that was also my guess. Should I report it on Github?

---

<div class="post-metadata">

### Author: ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)
#### Post date: [December 10, 2019, 8:44am UTC](https://discuss.elastic.co/t/filebeat-error-watching-for-docker-events-context-deadline-exceeded/211113/4 "2019-12-10T08:44:48Z")

</div>

Hi @speechkey, yes if you can open an issue for this would be really appreciated.  
If so, please "cc" me in the description so as to handle it soonish.

Thanks a lot!

---

<div class="post-metadata">

### Author: ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)
#### Post date: [December 13, 2019, 3:08pm UTC](https://discuss.elastic.co/t/filebeat-error-watching-for-docker-events-context-deadline-exceeded/211113/5 "2019-12-13T15:08:20Z")

</div>

Hi in order to keep track of it I created the issue: [https://github.com/elastic/beats/issues/15096](https://github.com/elastic/beats/issues/15096)

Regards.

---

<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: [January 10, 2020, 3:08pm UTC](https://discuss.elastic.co/t/filebeat-error-watching-for-docker-events-context-deadline-exceeded/211113/6 "2020-01-10T15:08:27Z")

</div>

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