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

docker

(Jan Jansen) #1

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'

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


(Jaime Soriano) #2

Hi @farodin91 and welcome :slight_smile:

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?


(Jan Jansen) #3

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".


(Jaime Soriano) #4

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

Thanks for reporting!


(Jan Jansen) #5

Thank you for the fast response.