From 746f0be2e7153bf0f6fdbc8beef48cc5287d5c94 Mon Sep 17 00:00:00 2001 From: Adam Hill Date: Sat, 22 Oct 2016 12:29:28 -0500 Subject: [PATCH] Update README.md --- README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index a24c796..1f5b546 100644 --- a/README.md +++ b/README.md @@ -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