# Error creating runner from config: reading docker input config: missing field accessing 'containers.ids.0'

**URL:** <https://discuss.elastic.co/t/error-creating-runner-from-config-reading-docker-input-config-missing-field-accessing-containers-ids-0/158589>\
**Category:** Beats\
**Tags:** docker, filebeat\
**Created:** [November 28, 2018, 2:44pm UTC](https://discuss.elastic.co/t/error-creating-runner-from-config-reading-docker-input-config-missing-field-accessing-containers-ids-0/158589 "2018-11-28T14:44:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![farodin91](https://avatars.discourse-cdn.com/v4/letter/f/977dab/32.png) [@farodin91](https://discuss.elastic.co/u/farodin91)\
**Post date:** [November 28, 2018, 2:44pm UTC](https://discuss.elastic.co/t/error-creating-runner-from-config-reading-docker-input-config-missing-field-accessing-containers-ids-0/158589/1 "2018-11-28T14:44:58Z")

</div>

I have the same bug for docker container instead of kubernetes pods [Filebeat (6.4.2) autodiscover on Kubernetes. Missing field accessing 'containers.ids.0'](https://discuss.elastic.co/t/filebeat-6-4-2-autodiscover-on-kubernetes-missing-field-accessing-containers-ids-0/154459)

Please include configurations and logs if available.

```
2018-11-28T14:19:07.054Z	INFO	log/input.go:138	Configured paths: [/var/lib/docker/containers/2d33e4684aae2a8dc5b504fbdd8337c532f1cec880a45c572fe30a3d17693006/*.log]
2018-11-28T14:19:07.054Z	INFO	input/input.go:114	Starting input of type: docker; ID: 17821001299542660013 
2018-11-28T14:19:07.058Z	ERROR	[autodiscover]	cfgfile/list.go:96	Error creating runner from config: reading docker input config: missing field accessing 'containers.ids.0'
2018-11-28T14:19:07.059Z	ERROR	[autodiscover]	cfgfile/list.go:96	Error creating runner from config: reading docker input config: missing field accessing 'containers.ids.0'

```

config:

```
logging.metrics.enabled: false

filebeat.registry_file: ${path.data}/registry

filebeat.config.modules:
  path: ${path.config}/modules.d/*.yml

filebeat.autodiscover:
  providers:
    - type: docker
      hints.enabled: true

fields:
  env: ${swarm.environment}

output.logstash:
  hosts: ["${logstash.url}:${logstash.port}"]

```

Version: [docker.elastic.co/beats/filebeat:6.5.1](http://docker.elastic.co/beats/filebeat:6.5.1)

---

<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:** [November 28, 2018, 4:51pm UTC](https://discuss.elastic.co/t/error-creating-runner-from-config-reading-docker-input-config-missing-field-accessing-containers-ids-0/158589/2 "2018-11-28T16:51:09Z")

</div>

Hi @farodin91 and welcome 🙂

What behaviour are you observing? Are logs being collected even if you see this error? or it is not collecting logs from containers?

Could you share the labels you are using for hints-based configuration?

---

<div class="post-metadata">

**Author:** ![farodin91](https://avatars.discourse-cdn.com/v4/letter/f/977dab/32.png) [@farodin91](https://discuss.elastic.co/u/farodin91)\
**Post date:** [November 29, 2018, 7:06am UTC](https://discuss.elastic.co/t/error-creating-runner-from-config-reading-docker-input-config-missing-field-accessing-containers-ids-0/158589/3 "2018-11-29T07:06:31Z")

</div>

Hi @jsoriano

What behaviour are you observing?  
I updated from 6.3.1 to 6.5.1 without changing the config and now i see these error logs.

Are logs being collected even if you see this error?  
Logs are collected as before.

Could you share the labels you are using for hints-based configuration?  
For the logstash and filebeat container, we have set the label: `co.elastic.logs/disable="true"`.

---

<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:** [November 30, 2018, 1:00pm UTC](https://discuss.elastic.co/t/error-creating-runner-from-config-reading-docker-input-config-missing-field-accessing-containers-ids-0/158589/4 "2018-11-30T13:00:08Z")

</div>

Hi @farodin91,

After investigating a little bit we have found that there can be some misbehaviours when the `disable` hint is used. I have opened a PR to address them [https://github.com/elastic/beats/pull/9305](https://github.com/elastic/beats/pull/9305)

Thanks for reporting!

---

<div class="post-metadata">

**Author:** ![farodin91](https://avatars.discourse-cdn.com/v4/letter/f/977dab/32.png) [@farodin91](https://discuss.elastic.co/u/farodin91)\
**Post date:** [December 3, 2018, 7:34am UTC](https://discuss.elastic.co/t/error-creating-runner-from-config-reading-docker-input-config-missing-field-accessing-containers-ids-0/158589/5 "2018-12-03T07:34:48Z")

</div>

Thank you for the fast response.

---

<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:** [December 31, 2018, 7:38am UTC](https://discuss.elastic.co/t/error-creating-runner-from-config-reading-docker-input-config-missing-field-accessing-containers-ids-0/158589/6 "2018-12-31T07:38:20Z")

</div>

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