# \[Filebeat\] Using the System module while running Filebeat in docker
**URL:** https://discuss.elastic.co/t/filebeat-using-the-system-module-while-running-filebeat-in-docker/239700
**Category:** Beats
**Tags:** docker, filebeat
**Created:** [July 2, 2020, 6:41pm UTC](https://discuss.elastic.co/t/filebeat-using-the-system-module-while-running-filebeat-in-docker/239700 "2020-07-02T18:41:49Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@miande](https://discuss.elastic.co/u/miande)
#### Post date: [July 2, 2020, 6:41pm UTC](https://discuss.elastic.co/t/filebeat-using-the-system-module-while-running-filebeat-in-docker/239700/1 "2020-07-02T18:41:49Z")
When running Filebeat as a docker container and using the System module in the filebeat.yml it requires access to the host's file system for reading from /var/logs/ (easy enough) but once the System module pulls the logs you must also use the processor "add\_process\_metadata" which the (Filebeat) container doesn't have access nor a configuration to the host's /proc (process ids) to get the syslog process.\* details. Is this a known issue?
(more background) Metricbeat has overcome this issue with the "add\_process\_metadata" via use of the --system.hostfs configuration.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 30, 2020, 8:41pm UTC](https://discuss.elastic.co/t/filebeat-using-the-system-module-while-running-filebeat-in-docker/239700/2 "2020-07-30T20:41:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.