From f2e9d32eda52d6b268f1202fd0dc13246cea503f Mon Sep 17 00:00:00 2001 From: Brendan Tobolaski Date: Sat, 22 Mar 2014 21:50:06 -0500 Subject: [PATCH] Fix upgrade instructions with a new container If you attempt to bootstrap a new container without stopping or destroying the original it will fail because postgres will detect that it is running in another container. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f01957b..de611ea 100644 --- a/README.md +++ b/README.md @@ -123,8 +123,8 @@ The Docker setup gives you multiple upgrade options: 1. Use the front end at http://yoursite.com/admin/docker to upgrade an already running image. 2. Create a new base image by running: - - `./launcher bootstrap my_image` - `./launcher destroy my_image` + - `./launcher bootstrap my_image` - `./launcher start my_image` ### Single Container vs. Multiple Container -- 2.25.1