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 1/2] 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. From 34853e703905e1c212c9f376d86198b8c82f1950 Mon Sep 17 00:00:00 2001 From: wuyangfan <1102042793@qq.com> Date: Sun, 17 May 2026 19:09:54 +0800 Subject: [PATCH 2/2] docs: use verb phrase "set up" instead of "setup" Use "set up" for verb usages while keeping "setup" as a noun where appropriate. Fixes prometheus/docs#2878 Co-authored-by: Cursor --- docs/introduction/overview.md | 2 +- docs/tutorials/alerting_based_on_metrics.md | 2 +- docs/tutorials/getting_started.md | 2 +- docs/tutorials/visualizing_metrics_using_grafana.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/introduction/overview.md b/docs/introduction/overview.md index 6eeb7c9fe..8d368f0f5 100644 --- a/docs/introduction/overview.md +++ b/docs/introduction/overview.md @@ -78,7 +78,7 @@ Prometheus is designed for reliability, to be the system you go to during an outage to allow you to quickly diagnose problems. Each Prometheus server is standalone, not depending on network storage or other remote services. You can rely on it when other parts of your infrastructure are broken, and -you do not need to setup extensive infrastructure to use it. +you do not need to set up extensive infrastructure to use it. ## When does it not fit? diff --git a/docs/tutorials/alerting_based_on_metrics.md b/docs/tutorials/alerting_based_on_metrics.md index acd0299b9..9b74114ca 100644 --- a/docs/tutorials/alerting_based_on_metrics.md +++ b/docs/tutorials/alerting_based_on_metrics.md @@ -12,7 +12,7 @@ Download the latest release of Alertmanager for your operating system from [here Alertmanager supports various receivers like `email`, `webhook`, `pagerduty`, `slack` etc through which it can notify when an alert is firing. You can find the list of receivers and how to configure them [here](/docs/alerting/latest/configuration/). We will use `webhook` as a receiver for this tutorial, head over to [webhook.site](https://webhook.site) and copy the webhook URL which we will use later to configure the Alertmanager. -First let's setup Alertmanager with the webhook receiver. +First let's set up Alertmanager with the webhook receiver. > alertmanager.yml diff --git a/docs/tutorials/getting_started.md b/docs/tutorials/getting_started.md index 7dcc7dc43..10b104a55 100644 --- a/docs/tutorials/getting_started.md +++ b/docs/tutorials/getting_started.md @@ -53,7 +53,7 @@ One can scrape multiple useful metrics to understand what is happening in the ap ## Show me how it is done -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. +Let’s get our hands dirty and set up 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 diff --git a/docs/tutorials/visualizing_metrics_using_grafana.md b/docs/tutorials/visualizing_metrics_using_grafana.md index b5dda2b3c..8de9d4723 100644 --- a/docs/tutorials/visualizing_metrics_using_grafana.md +++ b/docs/tutorials/visualizing_metrics_using_grafana.md @@ -13,7 +13,7 @@ Grafana and [Console Templates](https://prometheus.io/docs/visualization/console Install and Run Grafana by following the steps from [here](https://grafana.com/docs/grafana/latest/installation/requirements/#supported-operating-systems) for your operating system. -Once Grafana is installed and run, navigate to [http://localhost:3000](http://localhost:3000) in your browser. Use the default credentials, username as `admin` and password as `admin` to log in and setup new credentials. +Once Grafana is installed and run, navigate to [http://localhost:3000](http://localhost:3000) in your browser. Use the default credentials, username as `admin` and password as `admin` to log in and set up new credentials. ## Adding Prometheus as a Data Source in Grafana.