# Filebeat: Persist processed logs if docker container crashes

**URL:** <https://discuss.elastic.co/t/filebeat-persist-processed-logs-if-docker-container-crashes/60089>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 8, 2016, 3:35pm UTC](https://discuss.elastic.co/t/filebeat-persist-processed-logs-if-docker-container-crashes/60089 "2016-09-08T15:35:34Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [September 9, 2016, 6:15am UTC](https://discuss.elastic.co/t/filebeat-persist-processed-logs-if-docker-container-crashes/60089/4 "2016-09-09T06:15:06Z")

</div>

Alternatively instead of running filebeat in each container, you could run one container with filebeat and mount the docker logs volumes into the container for processing. Liek this filebeat keeps running if one of your containers stops.

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-persist-processed-logs-if-docker-container-crashes/60089)._