# Add\_docker\_metadata cannot process containers that already exited

**URL:** <https://discuss.elastic.co/t/add-docker-metadata-cannot-process-containers-that-already-exited/335435>\
**Category:** Beats\
**Tags:** docker, libbeat\
**Created:** [June 7, 2023, 11:46am UTC](https://discuss.elastic.co/t/add-docker-metadata-cannot-process-containers-that-already-exited/335435 "2023-06-07T11:46:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Maciej\_Piasecki](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maciej_piasecki/32/121836_2.png) [@Maciej\_Piasecki](https://discuss.elastic.co/u/Maciej_Piasecki)\
**Post date:** [June 7, 2023, 11:46am UTC](https://discuss.elastic.co/t/add-docker-metadata-cannot-process-containers-that-already-exited/335435/1 "2023-06-07T11:46:29Z")

</div>

For the input type **container** if the log file is discovered after the container is stopped, the add\_metadata\_processor reports

```auto
{"file.name":"add_docker_metadata/add_docker_metadata.go","file.line":213},"message":"Container not found: cid=b8f04dcf8a6c222c234219d1116bea0be37c74432ad779d0dc4a8edc7072b056",
"service.name":"filebeat","ecs.version":"1.6.0"}

```

and no container metadata is added.  
Is this a desired behavior or a bug?

---

<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:** [July 5, 2023, 1:46pm UTC](https://discuss.elastic.co/t/add-docker-metadata-cannot-process-containers-that-already-exited/335435/2 "2023-07-05T13:46:40Z")

</div>

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