You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[](https://hub.docker.com/r/nginxproxy/nginx-proxy"Click to view the image on Docker Hub")
nginx-proxy sets up a container running nginx and [docker-gen](https://github.com/nginx-proxy/docker-gen). docker-gen generates reverse proxy configs for nginx and reloads nginx when containers are started and stopped.
Then start any containers (here an nginx container) you want proxied with an env var `VIRTUAL_HOST=subdomain.yourdomain.com`
@@ -34,6 +33,7 @@ docker run --detach \
34
33
Provided your DNS is setup to resolve `foo.bar.com` to the host running nginx-proxy, a request to `http://foo.bar.com` will then be routed to a container with the `VIRTUAL_HOST` env var set to `foo.bar.com` (in this case, the **your-proxied-app** container).
35
34
36
35
The containers being proxied must :
36
+
37
37
-[expose](https://docs.docker.com/engine/reference/run/#expose-incoming-ports) the port to be proxied, either by using the `EXPOSE` directive in their `Dockerfile` or by using the `--expose` flag to `docker run` or `docker create`.
38
38
- share at least one Docker network with the nginx-proxy container: by default, if you don't pass the `--net` flag when your nginx-proxy container is created, it will only be attached to the default bridge network. This means that it will not be able to connect to containers on networks other than bridge.
39
39
@@ -48,22 +48,22 @@ The nginx-proxy images are available in two flavors.
48
48
This image is based on the nginx:mainline image, itself based on the debian slim image.
49
49
50
50
```console
51
-
docker pull nginxproxy/nginx-proxy:1.4
51
+
docker pull nginxproxy/nginx-proxy:1.6
52
52
```
53
53
54
54
#### Alpine based version (`-alpine` suffix)
55
55
56
56
This image is based on the nginx:alpine image.
57
57
58
58
```console
59
-
docker pull nginxproxy/nginx-proxy:1.4-alpine
59
+
docker pull nginxproxy/nginx-proxy:1.6-alpine
60
60
```
61
61
62
62
#### :warning: a note on `latest` and `alpine`:
63
63
64
64
It is not recommended to use the `latest` (`nginxproxy/nginx-proxy`, `nginxproxy/nginx-proxy:latest`) or `alpine` (`nginxproxy/nginx-proxy:alpine`) tag for production setups.
65
65
66
-
Those tags points to the latest commit in the `main` branch. They do not carry any promise of stability, and using them will probably put your nginx-proxy setup at risk of experiencing uncontrolled updates to non backward compatible versions (or versions with breaking changes). You should always specify the version you want to use explicitly to ensure your setup doesn't break when the image is updated.
66
+
[Those tags point](https://hub.docker.com/r/nginxproxy/nginx-proxy/tags) to the latest commit in the `main` branch. They do not carry any promise of stability, and using them will probably put your nginx-proxy setup at risk of experiencing uncontrolled updates to non backward compatible versions (or versions with breaking changes). You should always specify the version you want to use explicitly to ensure your setup doesn't break when the image is updated.
0 commit comments