From 105dbec480c546b87f8d02bd53695c075d6503ba Mon Sep 17 00:00:00 2001
From: Robert Fratto <robert.fratto@grafana.com>
Date: Tue, 10 Sep 2019 16:09:29 -0400
Subject: [PATCH] docs: fix example with pulling systemd logs

/etc/machine-id must be mounted in the container for promtail to know
which systemd journal to read from.
---
 docs/promtail/config-examples.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/promtail/config-examples.md b/docs/promtail/config-examples.md
index 52b7c929..a7497dc7 100644
--- a/docs/promtail/config-examples.md
+++ b/docs/promtail/config-examples.md
@@ -128,12 +128,14 @@ in Loki. All other labels from the journal entry are dropped.
 ### Example Use
 
 `promtail` must have access to the journal path (`/var/log/journal`)
-where journal entries are stored for journal support to work correctly.
+where journal entries are stored and the machine ID (`/etc/machine-id`) for
+journal support to work correctly.
 
-If running with Docker, that means to bind that path:
+If running with Docker, that means to bind those paths:
 
 ```bash
 docker run -d --name promtail --network loki_network -p 9080:9080 \
   -v /var/log/journal:/var/log/journal \
+  -v /etc/machine-id:/etc/machine-id \
   mypromtail-image -config.file=/etc/promtail/my-systemd-journal-config.yaml
 ```
-- 
GitLab