1
1
# Advanced Configuration
2
2
3
- ## Best Practice: Use a docker network
3
+ ## Best Practice: Use a Docker network
4
4
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.
8
8
9
9
Create a network, ie "scoobydoo":
10
10
@@ -13,7 +13,7 @@ docker network create scoobydoo
13
13
```
14
14
15
15
Then 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:
17
17
18
18
``` yml
19
19
networks :
@@ -44,13 +44,13 @@ networks:
44
44
45
45
Now in the NPM UI you can create a proxy host with ` portainer` as the hostname,
46
46
and 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
49
49
hostname, so make sure your service names are unique when using the same network.
50
50
51
51
# # Docker Healthcheck
52
52
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
54
54
feature by adding the following to the service in your `docker-compose.yml` file :
55
55
56
56
` ` ` yml
@@ -128,7 +128,7 @@ services:
128
128
129
129
# # Disabling IPv6
130
130
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 :
132
132
133
133
> Address family not supported by protocol
134
134
0 commit comments