Startup Docker race condition

Elastic Stack Beats
,
1

Facing an issue when a server reboots with Filebeat 7.10 and Docker. Filebeat will start slightly before Docker and not pick up Docker container logs. If you restart Filebeat, it will then pick them up. I could set startup delays/dependencies at the system level, but I feel like there should be a better solution for this. Here is my filebeat.yml config

filebeat.autodiscover:
  providers:
    - type: docker
      hints.enabled: true
      templates:
        - condition:
            contains:
              docker.container.id: '*'
          config:
            - type: docker
              containers.ids:
                - "${data.docker.container.id}"
2

What do the Filebeat logs show when this happens? Can you enable debug and then restart things to capture what's happening?

3

Turning on debug and disabling all logging except Docker, this is the only mention of Docker I see when filebeats starts:

DEBUG	[docker]	docker/client.go:48	Docker client will negotiate the API version on the first request.
4

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