From 6ad9e9eda607ad58b9794001761a68a5622fa68c Mon Sep 17 00:00:00 2001 From: Valeriy Sotnikov Date: Thu, 11 May 2023 23:51:21 +0300 Subject: [PATCH] sudo docker volume prune --filter all=1 Signed-off-by: Valeriy Sotnikov --- readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme.md b/readme.md index 51be2817..f0e4a14f 100644 --- a/readme.md +++ b/readme.md @@ -303,7 +303,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 docker --filter all=1` (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 --filter all=1` (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. 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. (E.g. by simply deleting the directory). 1. Make sure that no volumes are remaining with `sudo docker volume ls --format {{.Name}}`. If no `nextcloud-aio` volumes are listed, you can proceed with the steps below. If there should be some, you will need to stop them with `sudo docker volume rm ` until no one is listed anymore. 1. Optional: You can remove all docker images with `sudo docker image prune -a`.