From 1f6bfb10e6f8c65d1ff2aa53f6c75dcfc2c9f56a Mon Sep 17 00:00:00 2001 From: Adam Pyle Date: Mon, 18 May 2015 21:56:17 +1000 Subject: [PATCH 1/3] Update README.md Updated section on using nginx proxy - > container nginx .conf location was incorrect. > container nginx port mapping was incorrect The changes were made to work with existing transmission container --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index abb3cc8..f7f0521 100644 --- a/README.md +++ b/README.md @@ -92,7 +92,7 @@ This is because the VPN is active, and since docker is running in a different ip There are several ways to fix this. You can pipe and do fancy iptables or ip route configurations on the host and in the Docker image. But I found that the simplest solution is just to proxy my traffic. Start a Nginx container like this: ``` -$ docker run -d -v /path/to/nginx.conf:/etc/nginx.conf:ro -p 8080:80 nginx +$ docker run -d -v /path/to/nginx.conf:/etc/nginx/nginx.conf:ro -p 8080:8080 nginx ``` Where /path/to/nginx.conf has this content: From 51df6f58379d453f2ae633e0d7b771844fe0b6df Mon Sep 17 00:00:00 2001 From: Adam Pyle Date: Wed, 20 May 2015 17:18:19 +1000 Subject: [PATCH 2/3] Update README.md Updated port mapping back to default --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f7f0521..f15c267 100644 --- a/README.md +++ b/README.md @@ -92,7 +92,7 @@ This is because the VPN is active, and since docker is running in a different ip There are several ways to fix this. You can pipe and do fancy iptables or ip route configurations on the host and in the Docker image. But I found that the simplest solution is just to proxy my traffic. Start a Nginx container like this: ``` -$ docker run -d -v /path/to/nginx.conf:/etc/nginx/nginx.conf:ro -p 8080:8080 nginx +$ docker run -d -v /path/to/nginx.conf:/etc/nginx/nginx.conf:ro -p 8080:80 nginx ``` Where /path/to/nginx.conf has this content: From c51466556e158ae5d9fae159280afbf0dc032503 Mon Sep 17 00:00:00 2001 From: Adam Pyle Date: Wed, 20 May 2015 22:59:13 +1000 Subject: [PATCH 3/3] Update README.md Fixed minor port mistake --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f15c267..f7f0521 100644 --- a/README.md +++ b/README.md @@ -92,7 +92,7 @@ This is because the VPN is active, and since docker is running in a different ip There are several ways to fix this. You can pipe and do fancy iptables or ip route configurations on the host and in the Docker image. But I found that the simplest solution is just to proxy my traffic. Start a Nginx container like this: ``` -$ docker run -d -v /path/to/nginx.conf:/etc/nginx/nginx.conf:ro -p 8080:80 nginx +$ docker run -d -v /path/to/nginx.conf:/etc/nginx/nginx.conf:ro -p 8080:8080 nginx ``` Where /path/to/nginx.conf has this content: