# 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:** 2

<div class="post-metadata">

**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\
**Post date:** [February 19, 2018, 2:48pm UTC](https://discuss.elastic.co/t/using-autodiscover-feature-for-docker-does-not-work-when-running-in-swarm-mode/120342/2 "2018-02-19T14:48:27Z")

</div>

Hi @darkl0rd,

Thank you for testing Filebeat and providing feedback!

It seems mapping failed due to some of your labels, `com.docker.swarm.task` is currently holding an object, and a single keyword is being indexed (and failing). From what I see you probably have a set of lables like this:

```auto
  "com.docker.swarm.task": "",
  "com.docker.swarm.task.id": "xxxxx",
  "com.docker.swarm.task.name": "xxxxx"

```

This is an issue we have recently fixed (yet to be released), and it's related to the dots in label names and how Elasticsearch stores them.

Something you could do as of today is ignoring the `com.docker.swarm.task` field from Filebeat side, to avoid mapping errors. You can do that by using the drop\_field processor:

```auto
processors:
- drop_fields:
  fields:
    - `docker.container.labels.com.docker.swarm.task`

```

---

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