# How to handle log duplications on docker restart
**URL:** https://discuss.elastic.co/t/how-to-handle-log-duplications-on-docker-restart/123183
**Category:** Beats
**Created:** [March 9, 2018, 3:59am UTC](https://discuss.elastic.co/t/how-to-handle-log-duplications-on-docker-restart/123183 "2018-03-09T03:59:36Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@idangozlan](https://discuss.elastic.co/u/idangozlan)
#### Post date: [March 9, 2018, 3:59am UTC](https://discuss.elastic.co/t/how-to-handle-log-duplications-on-docker-restart/123183/1 "2018-03-09T03:59:36Z")
Hi,
Im trying to understand how to handle cases that filebeat docker is restarted and start collect same logs line again.
I guess that there is a way to mount filebeat offset information, I didn't see any information about that, maybe im searching the wrong keywords.
Edit: is that right thing to do to mount filebeat/data:/usr/share/filebeat/data in order to prevent duplicates?
Thanks
---
### Author:  [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [March 12, 2018, 10:22am UTC](https://discuss.elastic.co/t/how-to-handle-log-duplications-on-docker-restart/123183/2 "2018-03-12T10:22:31Z")
Yes, the data directory stores the registry file which has all the information about which files were already read. You should make sure that this is persisted and reused.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 9, 2018, 12:22pm UTC](https://discuss.elastic.co/t/how-to-handle-log-duplications-on-docker-restart/123183/3 "2018-04-09T12:22:36Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.