From 7fe3a708dd25a0b1eae9fbb96fc72c0296cbbb81 Mon Sep 17 00:00:00 2001 From: MadelineMurray <43356962+MadelineMurray@users.noreply.github.com> Date: Mon, 14 Jan 2019 10:56:45 +1100 Subject: [PATCH] Added caution and recovery steps for v0.8.3 Docker bug --- docs/Getting-Started/Run-Docker-Image.md | 29 ++++++++++++++++++++---- 1 file changed, 25 insertions(+), 4 deletions(-) diff --git a/docs/Getting-Started/Run-Docker-Image.md b/docs/Getting-Started/Run-Docker-Image.md index 0e502e3822..c97af780d0 100644 --- a/docs/Getting-Started/Run-Docker-Image.md +++ b/docs/Getting-Started/Run-Docker-Image.md @@ -7,6 +7,29 @@ A Docker image is provided to run a Pantheon node in a Docker container. Use this Docker image to run a single Pantheon node without installing Pantheon. +!!!caution + If you have been running a node using the v0.8.3 Docker image, the node was not saving data to the + specified [data directory](#data-directory), or referring to the custom [configuration file](#custom-configuration-file) + or [genesis file](#custom-genesis-file). + + To recover the node key and data directory from the Docker container: + + `docker cp :/opt/pantheon/key ` + + `docker cp :/opt/pantheon/database ` + + Where `container` is the name or ID of the Docker container containing the Pantheon node. + + The container can be running or stopped when you copy the key and data directory. If your node was + fully synchronized to MainNet, the data directory will be ~2TB. + + When restarting your node with the v0.8.4 Docker image: + + * Save the node key in the [`key` file](../Configuring-Pantheon/Node-Keys.md#node-private-key) in the data + directory or specify the location using the [`--node-private-key` option](../Configuring-Pantheon/Node-Keys.md#specifying-a-custom-node-private-key-file). + + * Specify the `