mirror of
https://github.com/nextcloud/all-in-one.git
synced 2026-02-16 18:50:20 +00:00
documentation: use force to prune docker resources
In the documentation there is reference of a manipulation to perform in case the collabora container is missing some permissions to access the filesystem, however `docker system prune` might not clean what's needed. Adding `-a` is very broad however but will most definitely clean the image. Fixes #6776 Signed-off-by: Thomas Lavocat <tlavocat@redhat.com>
This commit is contained in:
parent
6d147a99cf
commit
afde995ac6
1 changed files with 1 additions and 1 deletions
|
|
@ -409,7 +409,7 @@ You can move the whole docker library and all its files including all Nextcloud
|
||||||
|
|
||||||
1. Stop all the containers from the AIO Interface.
|
1. Stop all the containers from the AIO Interface.
|
||||||
2. Go to your terminal and delete the Collabora container (`docker rm nextcloud-aio-collabora`) AND the Collabora image (`docker image rm nextcloud/aio-collabora`).
|
2. Go to your terminal and delete the Collabora container (`docker rm nextcloud-aio-collabora`) AND the Collabora image (`docker image rm nextcloud/aio-collabora`).
|
||||||
3. You might also want to prune your Docker (`docker system prune`) (no data will be lost).
|
3. You might also want to prune your Docker (`docker system prune -a`) (no data will be lost).
|
||||||
4. Restart your containers from the AIO Interface.
|
4. Restart your containers from the AIO Interface.
|
||||||
|
|
||||||
This should solve the problem.
|
This should solve the problem.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue