From cd749c8de72c87d87224bc75e152e0c6c4a9855e Mon Sep 17 00:00:00 2001 From: wuyangfan <1102042793@qq.com> Date: Sun, 17 May 2026 19:02:21 +0800 Subject: [PATCH] docs: note Prometheus Docker images run as nobody Document the default container user and volume permission requirements for bind-mounted config and TSDB paths. Fixes prometheus/docs#2470 Co-authored-by: Cursor --- docs/tutorials/getting_started.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/tutorials/getting_started.md b/docs/tutorials/getting_started.md index bd092c768..7dcc7dc43 100644 --- a/docs/tutorials/getting_started.md +++ b/docs/tutorials/getting_started.md @@ -55,6 +55,10 @@ One can scrape multiple useful metrics to understand what is happening in the ap Let’s get our hands dirty and setup Prometheus. Prometheus is written using [Go](https://golang.org/) and all you need is the binary compiled for your operating system. Download the binary corresponding to your operating system from [here](https://prometheus.io/download/) and add the binary to your path. +### Running with Docker + +Official Prometheus container images run as the `nobody` user by default. If you bind-mount host paths for configuration or TSDB storage, make sure those directories are readable and writable by UID/GID 65534 (`nobody`), or run the container with a user that matches your host permissions. Running the container as root does not change this default user inside the image. + Prometheus exposes its own metrics which can be consumed by itself or another Prometheus server. Now that we have Prometheus installed, the next step is to run it. All that we need is just the binary and a configuration file. Prometheus uses yaml files for configuration.