From 2e92a82a833bd7537e0ecffea6eee17f673d72ba Mon Sep 17 00:00:00 2001 From: szaimen Date: Mon, 16 May 2022 13:31:10 +0200 Subject: [PATCH] also stop the apache container Signed-off-by: szaimen --- manual-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual-upgrade.md b/manual-upgrade.md index ec5e4b03..cf52eb8c 100644 --- a/manual-upgrade.md +++ b/manual-upgrade.md @@ -6,7 +6,7 @@ The only way to fix this on your side is upgrading regularly (e.g. by enabling d 1. Start all containers from the aio interface (now, it will report that Nextcloud is restarting because it is not able to start due to the above mentioned problem) 1. Do **not** click on `Stop containers` because you will need them running going forward, see below -1. Stop the Nextcloud container by running `sudo docker stop nextcloud-aio-nextcloud`. +1. Stop the Nextcloud container and the Apache container by running `sudo docker stop nextcloud-aio-nextcloud && sudo docker stop nextcloud-aio-apache`. 1. Find out with which PHP version your installed Nextcloud is compatible by running `sudo cat /var/lib/docker/volumes/nextcloud_aio_nextcloud/_data/lib/versioncheck.php`. (There you will find information about the max. supported PHP version.) 1. Run the following commands in order to reverse engineer the Nextcloud container: ```bash