From edcfae8f8004cabe39189c38be6f5781b31e19f7 Mon Sep 17 00:00:00 2001
From: Clay-Mysten <100217682+Clay-Mysten@users.noreply.github.com>
Date: Fri, 15 Jul 2022 11:32:09 -0600
Subject: [PATCH] Add Docker Compose reset instructions to Fullnode doc (#3218)

---
 doc/src/build/fullnode.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/doc/src/build/fullnode.md b/doc/src/build/fullnode.md
index 9b0314ccf8494..acf4ab3006920 100644
--- a/doc/src/build/fullnode.md
+++ b/doc/src/build/fullnode.md
@@ -122,7 +122,7 @@ source.
 
 Follow the instructions in the
 [Fullnode Docker README](https://github.com/MystenLabs/sui/tree/main/docker/fullnode#readme)
-to run a Sui fullnode using Docker.
+to run a Sui fullnode using Docker, including [resetting the environment](https://github.com/MystenLabs/sui/tree/main/docker/fullnode#reset-the-environment).
 
 ### Building from source
 
@@ -220,6 +220,14 @@ typically wiped clean. In order to have your fullnode continue to properly
 synchronize with the new state of Devnet, you'll need to follow a few steps
 based on how you originally set up your node. See below.
 
+## With Docker Compose
+
+Follow the instructions to [reset the environment](https://github.com/MystenLabs/sui/tree/main/docker/fullnode#reset-the-environment),
+namely by running the command:
+```shell
+$ docker-compose down --volumes
+```
+
 ### Built from source
 
 If you followed the instructions for [building from