# Using AutoDiscover feature for Docker does not work when running in Swarm mode

**URL:** <https://discuss.elastic.co/t/using-autodiscover-feature-for-docker-does-not-work-when-running-in-swarm-mode/120342>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 18, 2018, 10:14am UTC](https://discuss.elastic.co/t/using-autodiscover-feature-for-docker-does-not-work-when-running-in-swarm-mode/120342 "2018-02-18T10:14:43Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![darkl0rd](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@darkl0rd](https://discuss.elastic.co/u/darkl0rd)\
**Post date:** [February 19, 2018, 5:52pm UTC](https://discuss.elastic.co/t/using-autodiscover-feature-for-docker-does-not-work-when-running-in-swarm-mode/120342/3 "2018-02-19T17:52:13Z")

</div>

Hi @exekias,

Correct, on the labels; these are the labels as they are added by Docker Swarm.  
Good to hear that this was recently fixed, for the record though - this issue can be reproduced on a single swarm node/single filebeat instance. The value of the label 'com.docker.swarm.task' always triggers this errors.

I have implemented your suggested workaround; which as expected resolves the issue.  
Minor note for others who might read this, it should be:

```auto
processors:
  - drop_fields:
      fields:
        - "docker.containers.labels"

```

(fields should be indented from drop\_fields).

Thanks for your help.

---

_[View the full topic](https://discuss.elastic.co/t/using-autodiscover-feature-for-docker-does-not-work-when-running-in-swarm-mode/120342)._