# Error with filebeat on kubernetes 1.20 using add\_kubernetes\_metadata **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [December 15, 2020, 2:20pm UTC](https://discuss.elastic.co/t/error-with-filebeat-on-kubernetes-1-20-using-add-kubernetes-metadata/258722 "2020-12-15T14:20:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![yoannma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yoannma/32/80362_2.png) [@yoannma](https://discuss.elastic.co/u/yoannma)\ **Post date:** [December 15, 2020, 2:20pm UTC](https://discuss.elastic.co/t/error-with-filebeat-on-kubernetes-1-20-using-add-kubernetes-metadata/258722/1 "2020-12-15T14:20:39Z")
Hello, I installed filebeat `7.10.1` on a kubernetes cluster `1.20` using the DaemonSet from [https://github.com/elastic/beats/blob/master/deploy/kubernetes/filebeat/filebeat-configmap.yaml](https://github.com/elastic/beats/blob/master/deploy/kubernetes/filebeat/filebeat-configmap.yaml) Using the hints based autodiscover, if I add the `add_kubernetes_metadata ` processor, I'm getting the error on every log file being processed : ``` add_kubernetes_metadata/matchers.go:91 Error extracting container id - source value does not contain matcher's logs_path '/var/lib/docker/containers/'. ``` I checked and I have the containers' logs in both folders `/var/log/containers/` and `/var/log/containers/`. It was working under kubernetes 1.18.13 without issue (`add_kubernetes_metadata` enabled) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 12, 2021, 4:20pm UTC](https://discuss.elastic.co/t/error-with-filebeat-on-kubernetes-1-20-using-add-kubernetes-metadata/258722/2 "2021-01-12T16:20:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.