-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Docker documentation #376
Conversation
--net="host" \ | ||
quay.io/prometheus/node-exporter \ | ||
-collector.procfs /host/proc \ | ||
-collector.sysfs /host/proc \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/host/sys
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ops, thanks - fixed. Copied it without checking from the issue.
bf9f8fd
to
8d9edf2
Compare
You can deploy this exporter using the [prom/node-exporter](https://registry.hub.docker.com/u/prom/node-exporter/) Docker image. | ||
|
||
For example: | ||
It's not recommended to deploy the node-exporter as Docker container because it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
node_exporter
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed!
|
||
For example: | ||
It's not recommended to deploy the node-exporter as Docker container because it | ||
requires access to the host system. If you need to run it on Docker, you can |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe "designed to monitor the host system"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SuperQ I went for a more technical description. Why do you think 'designed to monitor' is better than 'requires access to'? I imaging if we use the former, people might say: "well, designed for - but I still want to run it in Docker and Prometheus peepz don't allow it"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe to make it overly clear, mention both aspects. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. Like this?
8d9edf2
to
b681b93
Compare
This adds bind-mounts and ignore flags to Docker example and explains why it's best run uncontainerized.
b681b93
to
21173e2
Compare
@SuperQ Good to merge? |
Add NetClassByIface
This adds bind-mounts and ignore flags to Docker example and explains
why it's best run uncontainerized.