Fix broken link to Polyverse in Docker documentation (#9426)
* Fix broken link * Fix other broken link
Joel Hans committed
Jun 26, 2020 at 07:47 UTC
145ba882e8b778b3f757f7bf5929fa9ccc230314
1 file changed
+5
-8
packaging/docker/README.md
+5
-8
@@ -1,9 +1,7 @@
1
<!--
2
----
2
title: "Install Netdata with Docker"
3
date: 2020-04-23
4
custom_edit_url: https://github.com/netdata/netdata/edit/master/packaging/docker/README.md
6
----
5
-->
6
7
# Install the Netdata Agent with Docker
@@ -36,10 +34,9 @@ documentation](https://docs.docker.com/engine/reference/builder/#understand-how-
34
35
### Package scrambling in runtime (x86_64 only)
36
39
-Our x86_64 Docker images provide support for using [Polymorphic Polyverse
40
-Linux package scrambling](https://polyverse.io/how-it-works/) to protect
41
-against buffer overflow errors. To activate this, set the environemnt
42
-variable `RESCRAMBLE=true` while starting Netdata with a Docker container.
37
+Our x86_64 Docker images provide support for using [Polymorphic Polyverse Linux package
38
+scrambling](https://polyverse.com/products/polymorphing-linux-security/) to protect against buffer overflow errors. To
39
+activate this, set the environemnt variable `RESCRAMBLE=true` while starting Netdata with a Docker container.
40
41
## Run the Agent with the Docker command
42
@@ -160,8 +157,8 @@ your machine from within the container. Please read the following carefully.
157
#### Docker socket proxy (safest option)
158
159
Deploy a Docker socket proxy that accepts and filters out requests using something like
163
-[HAProxy](/docs/running-behind-haproxy/) so that it restricts connections to read-only access
164
-to the CONTAINERS endpoint.
160
+[HAProxy](/docs/Running-behind-haproxy.md) so that it restricts connections to read-only access to the CONTAINERS
161
+endpoint.
162
163
The reason it's safer to expose the socket to the proxy is because Netdata has a TCP port exposed outside the Docker
164
network. Access to the proxy container is limited to only within the network.