11# Advanced Configuration
22
3- ## Best Practice: Use a docker network
3+ ## Best Practice: Use a Docker network
44
5- For those who have a few of their upstream services running in docker on the same docker
6- host as NPM, here's a trick to secure things a bit better. By creating a custom docker network,
7- you don't need to publish ports for your upstream services to all of the docker host's interfaces.
5+ For those who have a few of their upstream services running in Docker on the same Docker
6+ host as NPM, here's a trick to secure things a bit better. By creating a custom Docker network,
7+ you don't need to publish ports for your upstream services to all of the Docker host's interfaces.
88
99Create a network, ie "scoobydoo":
1010
@@ -13,7 +13,7 @@ docker network create scoobydoo
1313```
1414
1515Then add the following to the ` docker-compose.yml ` file for both NPM and any other
16- services running on this docker host:
16+ services running on this Docker host:
1717
1818``` yml
1919networks :
@@ -44,13 +44,13 @@ networks:
4444
4545Now in the NPM UI you can create a proxy host with ` portainer` as the hostname,
4646and port `9000` as the port. Even though this port isn't listed in the docker-compose
47- file, it's "exposed" by the portainer docker image for you and not available on
48- the docker host outside of this docker network. The service name is used as the
47+ file, it's "exposed" by the Portainer Docker image for you and not available on
48+ the Docker host outside of this Docker network. The service name is used as the
4949hostname, so make sure your service names are unique when using the same network.
5050
5151# # Docker Healthcheck
5252
53- The `Dockerfile` that builds this project does not include a `HEALTCHECK ` but you can opt in to this
53+ The `Dockerfile` that builds this project does not include a `HEALTHCHECK ` but you can opt in to this
5454feature by adding the following to the service in your `docker-compose.yml` file :
5555
5656` ` ` yml
@@ -128,7 +128,7 @@ services:
128128
129129# # Disabling IPv6
130130
131- On some docker hosts IPv6 may not be enabled. In these cases, the following message may be seen in the log :
131+ On some Docker hosts IPv6 may not be enabled. In these cases, the following message may be seen in the log :
132132
133133> Address family not supported by protocol
134134
0 commit comments