docker/docker-pi-hole
1
0
Fork 0
mirror of https://github.com/pi-hole/docker-pi-hole.git synced 2024-06-28 20:20:57 +02:00
Code Issues Releases Wiki Activity

Merge pull request #270 from nxadm/master

Browse Source 
typo
This commit is contained in:
Adam Hill 2018-05-08 16:36:46 -05:00 committed by GitHub
commit 8e2889ba56
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -39,7 +39,7 @@ docker run -d \
```
Scripts that try to reach a blocked domain on port 443 will timeout because the domain is redirected to the docker host, while no service listens on port 443. Pages on the client will load very slowly on
sited doing this type of connection. Adding the port 443 forwarding to the container run results in a inmediate REJECT: the page will continue loading inmediately instead of waiting for the resource. An
sites doing this type of connection. Adding the port 443 forwarding to the container run results in a inmediate REJECT: the page will continue loading inmediately instead of waiting for the resource. An
alternative is instead of binding port 443 is blocking it by the firewall of the docker host, e.g. with `sudo ufw reject https`.
**This is just an example and might need changing.** Volumes are stored in the directory `$DOCKER_CONFIGS` and aren't required but are recommended for persisting data across docker re-creations for updating images. As mentioned on line 2, the auto `IP_LOOKUP` variable may not work for VPN tunnel interfaces.