[tor-commits] [community/develop] Add instructions on how to upgrade a container.

hiro at torproject.org hiro at torproject.org
Thu Jan 23 16:44:42 UTC 2020


commit 17bb36d926b9ad67af4dc7a504c8c36367d4a608
Author: Philipp Winter <phw at nymity.ch>
Date:   Tue Nov 26 09:25:21 2019 -0800

    Add instructions on how to upgrade a container.
---
 .../technical-setup/bridge/docker/contents.lr              | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr
index aff4cf2..9c7cf44 100644
--- a/content/relay-operations/technical-setup/bridge/docker/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr
@@ -40,7 +40,19 @@ That's it! Your container (identified by the first line of output) is now
 bootstrapping your new obfs4 bridge.  If you want to run more than one bridge on
 a single machine, run `make deploy` again, but with a different set of ports.
 
-### 3. Monitor your logs
+### 3. Upgrade a container
+
+To upgrade to the latest version of our image, you need to stop your existing
+container, delete it, pull the latest image, and finally deploy it:
+
+```
+docker stop CONTAINER_ID
+docker rm CONTAINER_ID
+docker pull phwinter/obfs4-bridge:latest
+make deploy OR_PORT=X PT_PORT=Y EMAIL=Z
+```
+
+### 4. Monitor your logs
 
 You can inspect your bridge's logs by running:
 





More information about the tor-commits mailing list