From 0523af0f8a3c8dd98387fe87ffe776b53d79fb23 Mon Sep 17 00:00:00 2001 From: szaimen Date: Sun, 25 Sep 2022 18:55:07 +0200 Subject: [PATCH] add a hint that the chosen datadir needs to be cleaned up as well Signed-off-by: szaimen --- readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme.md b/readme.md index 5b31e1b2..bfc991be 100644 --- a/readme.md +++ b/readme.md @@ -196,7 +196,7 @@ Here is how to reset the AIO instance properly: 1. Now remove all these stopped containers with `sudo docker container prune` 1. Delete the docker network with `sudo docker network rm nextcloud-aio` 1. Check which volumes are dangling with `sudo docker volume ls --filter "dangling=true"` -1. Now remove all these dangling volumes: `sudo docker volume prune` (on Windows you might need to remove some volumes afterwards manually with `docker volume rm nextcloud_aio_backupdir`, `docker volume rm nextcloud_aio_nextcloud_datadir`) +1. Now remove all these dangling volumes: `sudo docker volume prune` (on Windows you might need to remove some volumes afterwards manually with `docker volume rm nextcloud_aio_backupdir`, `docker volume rm nextcloud_aio_nextcloud_datadir`). Also if you've configured `NEXTCLOUD_DATADIR` to a path on your host instead of the default volume, you need to clean that up as well. 1. Optional: You can remove all docker images with `sudo docker image prune -a`. 1. And you are done! Now feel free to start over with the recommended docker run command!