docker
/
docker-pi-hole
mirror of https://github.com/pi-hole/docker-pi-hole.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Update README.md

This commit is contained in:
Adam Hill 2016-10-22 12:29:28 -05:00 committed by GitHub
parent f38fa10dd5
commit 746f0be2e7
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -88,16 +88,14 @@ The standard pi-hole customization abilities apply to this docker, but with dock
### Upgrading
For those unfamilar, the docker way to ugprade is:
**If you try to use `pi-hole -up` it will fail.** For those unfamilar, the docker way to ugprade is:
* Throw away your container: `docker rm -f pihole`
* If you care about your data (logs/customizations), make sure you have it volume mapped or it will be deleted in this step
* Download the latest version of the image: `docker pull diginc/pi-hole`
* Start your container with the newer base image: `docker run ... diginc/pi-hole` (whatever your original run command was)
Why is this style of upgrading good? A couple reasons: Everyone is starting from the same base which has been tested to known to work. No worrying about upgrading from A to B, B to C, or A to C is required for application developers.
**If you try to use `pi-hole -up` it will fail**, more about this is covered in [Issue 49](https://github.com/diginc/docker-pi-hole/issues/49)
Why is this style of upgrading good? A couple reasons: Everyone is starting from the same base image which has been tested to know it works. No worrying about upgrading from A to B, B to C, or A to C is required when rolling out updates, reducing complexity.
### Volumes customizations