From b996b979ad3ad9697234d083a673becb03d3b2fc Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Fri, 16 Jun 2023 16:44:40 -0500 Subject: [PATCH 01/11] Changes to our Nextcloud image Signed-off-by: Eric Nemchik --- content/issues/2023-06-16-nextcloud.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 content/issues/2023-06-16-nextcloud.md diff --git a/content/issues/2023-06-16-nextcloud.md b/content/issues/2023-06-16-nextcloud.md new file mode 100644 index 00000000..7baa70e2 --- /dev/null +++ b/content/issues/2023-06-16-nextcloud.md @@ -0,0 +1,26 @@ +--- +title: 'Notification: Changes to our Nextcloud image' +date: '2023-06-16 12:00:00Z' +informational: true +affected: + - 'Notifications' + - 'nextcloud' +section: issue +--- +We are releasing a new version of our [Nextcloud image](https://github.com/linuxserver/docker-nextcloud/) that is built with the Nextcloud application inside the image, rather than in the user `/config` volume. This means manually updating Nextcloud via command line will no longer be necessary or supported. The `updater.phar` command is completely removed. Installations for existing users will be migrated automatically when updating the container image. All future updates to your Nextcloud instance will happen via container image updates. + +**Updating via the admin web UI is not supported.** + +**Downgrading is not supported.** + +An important thing to keep in mind is that systems that automatically update your container will result in irreversible changes to your Nextcloud instance. We recommend pinning a specific tagged version like `lscr.io/linuxserver/nextcloud:27.0.0` and manually changing your image version when you are ready to upgrade. + +Excerpts from the updated README: + +### Updating Nextcloud + +Updating the Nextcloud container is done by pulling the new image, throwing away the old container and starting the new one. + +It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16. + +Since all data is stored in the `/config` and `/data` volumes, nothing gets lost. The startup script will check for the version in your volume and the installed docker version. If it finds a mismatch, it automatically starts the upgrade process. From e28a86352a34e309e54ff02bfcabfa7303394b0b Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Fri, 16 Jun 2023 17:09:13 -0500 Subject: [PATCH 02/11] Adjustments Signed-off-by: Eric Nemchik --- content/issues/2023-06-16-nextcloud.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/issues/2023-06-16-nextcloud.md b/content/issues/2023-06-16-nextcloud.md index 7baa70e2..5d78e93a 100644 --- a/content/issues/2023-06-16-nextcloud.md +++ b/content/issues/2023-06-16-nextcloud.md @@ -1,6 +1,6 @@ --- title: 'Notification: Changes to our Nextcloud image' -date: '2023-06-16 12:00:00Z' +date: '2023-06-16 22:00:00Z' informational: true affected: - 'Notifications' @@ -9,7 +9,7 @@ section: issue --- We are releasing a new version of our [Nextcloud image](https://github.com/linuxserver/docker-nextcloud/) that is built with the Nextcloud application inside the image, rather than in the user `/config` volume. This means manually updating Nextcloud via command line will no longer be necessary or supported. The `updater.phar` command is completely removed. Installations for existing users will be migrated automatically when updating the container image. All future updates to your Nextcloud instance will happen via container image updates. -**Updating via the admin web UI is not supported.** +**Updating via the admin web UI is no longer supported.** **Downgrading is not supported.** @@ -19,7 +19,7 @@ Excerpts from the updated README: ### Updating Nextcloud -Updating the Nextcloud container is done by pulling the new image, throwing away the old container and starting the new one. +Updating Nextcloud is done by pulling the new image, and recreating the container with it. It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16. From b4fd98c430e1cbe0384746ff2e5fef8bd7bfd5fb Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Mon, 19 Jun 2023 09:24:52 -0500 Subject: [PATCH 03/11] New date for nextcloud post Signed-off-by: Eric Nemchik --- .../issues/{2023-06-16-nextcloud.md => 2023-06-19-nextcloud.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename content/issues/{2023-06-16-nextcloud.md => 2023-06-19-nextcloud.md} (98%) diff --git a/content/issues/2023-06-16-nextcloud.md b/content/issues/2023-06-19-nextcloud.md similarity index 98% rename from content/issues/2023-06-16-nextcloud.md rename to content/issues/2023-06-19-nextcloud.md index 5d78e93a..c84ca70e 100644 --- a/content/issues/2023-06-16-nextcloud.md +++ b/content/issues/2023-06-19-nextcloud.md @@ -1,6 +1,6 @@ --- title: 'Notification: Changes to our Nextcloud image' -date: '2023-06-16 22:00:00Z' +date: '2023-06-19 22:00:00Z' informational: true affected: - 'Notifications' From ccd356c390f01b52f60eab1d74dd322328bb18da Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Mon, 19 Jun 2023 11:21:23 -0500 Subject: [PATCH 04/11] Add information about updating Nextcloud from older versions Signed-off-by: Eric Nemchik --- content/issues/2023-06-19-nextcloud.md | 37 ++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/content/issues/2023-06-19-nextcloud.md b/content/issues/2023-06-19-nextcloud.md index c84ca70e..3987ec68 100644 --- a/content/issues/2023-06-19-nextcloud.md +++ b/content/issues/2023-06-19-nextcloud.md @@ -24,3 +24,40 @@ Updating Nextcloud is done by pulling the new image, and recreating the containe It is only possible to upgrade one major version at a time. For example, if you want to upgrade from version 14 to 16, you will have to upgrade from version 14 to 15, then from 15 to 16. Since all data is stored in the `/config` and `/data` volumes, nothing gets lost. The startup script will check for the version in your volume and the installed docker version. If it finds a mismatch, it automatically starts the upgrade process. + +### Can't start Nextcloud + +If after updating your container image you receive a message along these lines: + +> Can't start Nextcloud because the version of the data (`#.#.#.#`) is more than one major version behind the docker image version (`#.#.#.#`) and upgrading more than one major version is not supported. Please run an image tagged for the major version `##` first." + +The version of Nextcloud that you have installed in your persistent `/config` volume will need to be updated using an older image before you can use the new image. + +| Image/Tag | PHP | Notes | +| - | - | - | +| `lscr.io/linuxserver/nextcloud:26.0.2-ls248` | 8.2 | Use this tag if your major version is 26 | +| `lscr.io/linuxserver/nextcloud:26.0.2-ls245` | 8.1 | Included for reference as the last tag released with PHP 8.1 | +| `lscr.io/linuxserver/nextcloud:25.0.4-ls229` | 8.1 | | +| `lscr.io/linuxserver/nextcloud:24.0.12-ls239` | 8.1 | Use this tag if your major version is 24 | +| `lscr.io/linuxserver/nextcloud:24.0.6-ls204` | 7.4 | Included for reference as the last tag released with PHP 7.4 | +| `lscr.io/linuxserver/nextcloud:23.0.4-ls184` | 7.4 | | +| `lscr.io/linuxserver/nextcloud:22.2.3-ls165` | 7.4 | | + +- Check your `/config/www/nextcloud/config/config.php` file or `/config/www/nextcloud/version.php` file to determine the version you have installed +- Switch your image to the corresponding major version from the table above (ex: your files indicate `24.x.x`, use `lscr.io/linuxserver/nextcloud:24.0.12-ls239`) and start the container +- Execute `docker exec -it nextcloud updater.phar` ***repeatedly*** until there are no more updates, or the updater says `This version of Nextcloud is not compatible with > PHP x.x` +- Check your files again to determine the version you have installed + - If your installed version is below 26, repeat the steps above until you get to version 26 + - If your installed version is 26 or 27, continue with the instructions below +- Switch your image to `lscr.io/linuxserver/nextcloud:27.0.0-ls250` and start the container. Note the `updater.phar` is no longer available, or needed +- Execute `docker logs nextcloud` and check for any issues (report [issues on GitHub](https://github.com/linuxserver/docker-nextcloud/issues)) +- As of posting this information, Nextclouod 27 is the latest current version. If you are reading this after a new major version of Nextcloud beyond 27 is released, check [releases on GitHub](https://github.com/linuxserver/docker-nextcloud/releases) and proceed to switch to the next major version tag one by one until you are current. Updating more than one major version at a time is not supported +- You should now be able to switch your image to `lscr.io/linuxserver/nextcloud` (no tag) if you prefer to run the latest image (although we do recommend pinning a specific version) +- Execute `docker exec -it nextcloud mv /config/nginx/site-confs/default.conf /config/nginx/site-confs/default.conf.bak` +- Execute `docker exec -it nextcloud mv /config/nginx/nginx.conf /config/nginx/nginx.conf.bak` +- Nextcloud should now be in a working state + +Optional: + +- If you had customized any of the nginx configs that were renamed above, compare the `.bak` file to the new live file and apply any customizations you require. Note the `root` line in `site-confs/default.conf` should be changed from `/config/www/nextcloud/` to `/app/www/public` +- Remove the `.bak` files From 1bf0d7f363a2744f84b0b4fcbda6c5702edd9f8d Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Wed, 21 Jun 2023 09:28:57 -0500 Subject: [PATCH 05/11] Update and rename 2023-06-19-nextcloud.md to 2023-06-22-nextcloud.md --- .../{2023-06-19-nextcloud.md => 2023-06-22-nextcloud.md} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename content/issues/{2023-06-19-nextcloud.md => 2023-06-22-nextcloud.md} (98%) diff --git a/content/issues/2023-06-19-nextcloud.md b/content/issues/2023-06-22-nextcloud.md similarity index 98% rename from content/issues/2023-06-19-nextcloud.md rename to content/issues/2023-06-22-nextcloud.md index 3987ec68..20e6bc09 100644 --- a/content/issues/2023-06-19-nextcloud.md +++ b/content/issues/2023-06-22-nextcloud.md @@ -1,6 +1,6 @@ --- title: 'Notification: Changes to our Nextcloud image' -date: '2023-06-19 22:00:00Z' +date: '2023-06-22 22:00:00Z' informational: true affected: - 'Notifications' @@ -49,7 +49,7 @@ The version of Nextcloud that you have installed in your persistent `/config` vo - Check your files again to determine the version you have installed - If your installed version is below 26, repeat the steps above until you get to version 26 - If your installed version is 26 or 27, continue with the instructions below -- Switch your image to `lscr.io/linuxserver/nextcloud:27.0.0-ls250` and start the container. Note the `updater.phar` is no longer available, or needed +- Switch your image to `lscr.io/linuxserver/nextcloud:27.0.0-ls252` and start the container. Note the `updater.phar` is no longer available, or needed - Execute `docker logs nextcloud` and check for any issues (report [issues on GitHub](https://github.com/linuxserver/docker-nextcloud/issues)) - As of posting this information, Nextclouod 27 is the latest current version. If you are reading this after a new major version of Nextcloud beyond 27 is released, check [releases on GitHub](https://github.com/linuxserver/docker-nextcloud/releases) and proceed to switch to the next major version tag one by one until you are current. Updating more than one major version at a time is not supported - You should now be able to switch your image to `lscr.io/linuxserver/nextcloud` (no tag) if you prefer to run the latest image (although we do recommend pinning a specific version) From 71ca978022dfb79d49e7060e60f68ddfc08a0fe7 Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Fri, 23 Jun 2023 12:46:27 -0500 Subject: [PATCH 06/11] Update dates Signed-off-by: Eric Nemchik --- .../issues/{2023-06-22-nextcloud.md => 2023-06-23-nextcloud.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename content/issues/{2023-06-22-nextcloud.md => 2023-06-23-nextcloud.md} (99%) diff --git a/content/issues/2023-06-22-nextcloud.md b/content/issues/2023-06-23-nextcloud.md similarity index 99% rename from content/issues/2023-06-22-nextcloud.md rename to content/issues/2023-06-23-nextcloud.md index 20e6bc09..768e81fd 100644 --- a/content/issues/2023-06-22-nextcloud.md +++ b/content/issues/2023-06-23-nextcloud.md @@ -1,6 +1,6 @@ --- title: 'Notification: Changes to our Nextcloud image' -date: '2023-06-22 22:00:00Z' +date: '2023-06-23 22:00:00Z' informational: true affected: - 'Notifications' From 755e8e71c082116fc54458278e0a84c9526c17e9 Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Fri, 23 Jun 2023 13:14:34 -0500 Subject: [PATCH 07/11] Switch to version- tags instead of -ls build tags Signed-off-by: Eric Nemchik --- content/issues/2023-06-23-nextcloud.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/content/issues/2023-06-23-nextcloud.md b/content/issues/2023-06-23-nextcloud.md index 768e81fd..02552046 100644 --- a/content/issues/2023-06-23-nextcloud.md +++ b/content/issues/2023-06-23-nextcloud.md @@ -35,21 +35,21 @@ The version of Nextcloud that you have installed in your persistent `/config` vo | Image/Tag | PHP | Notes | | - | - | - | -| `lscr.io/linuxserver/nextcloud:26.0.2-ls248` | 8.2 | Use this tag if your major version is 26 | +| `lscr.io/linuxserver/nextcloud:version-26.0.2` | 8.2 | Use this tag if your major version is 26 | | `lscr.io/linuxserver/nextcloud:26.0.2-ls245` | 8.1 | Included for reference as the last tag released with PHP 8.1 | -| `lscr.io/linuxserver/nextcloud:25.0.4-ls229` | 8.1 | | -| `lscr.io/linuxserver/nextcloud:24.0.12-ls239` | 8.1 | Use this tag if your major version is 24 | +| `lscr.io/linuxserver/nextcloud:version-25.0.4` | 8.1 | | +| `lscr.io/linuxserver/nextcloud:version-24.0.12` | 8.1 | Use this tag if your major version is 24 | | `lscr.io/linuxserver/nextcloud:24.0.6-ls204` | 7.4 | Included for reference as the last tag released with PHP 7.4 | -| `lscr.io/linuxserver/nextcloud:23.0.4-ls184` | 7.4 | | -| `lscr.io/linuxserver/nextcloud:22.2.3-ls165` | 7.4 | | +| `lscr.io/linuxserver/nextcloud:version-23.0.4` | 7.4 | | +| `lscr.io/linuxserver/nextcloud:version-22.2.3` | 7.4 | | - Check your `/config/www/nextcloud/config/config.php` file or `/config/www/nextcloud/version.php` file to determine the version you have installed -- Switch your image to the corresponding major version from the table above (ex: your files indicate `24.x.x`, use `lscr.io/linuxserver/nextcloud:24.0.12-ls239`) and start the container +- Switch your image to the corresponding major version from the table above (ex: your files indicate `24.x.x`, use `lscr.io/linuxserver/nextcloud:version-24.0.12`) and start the container - Execute `docker exec -it nextcloud updater.phar` ***repeatedly*** until there are no more updates, or the updater says `This version of Nextcloud is not compatible with > PHP x.x` - Check your files again to determine the version you have installed - If your installed version is below 26, repeat the steps above until you get to version 26 - If your installed version is 26 or 27, continue with the instructions below -- Switch your image to `lscr.io/linuxserver/nextcloud:27.0.0-ls252` and start the container. Note the `updater.phar` is no longer available, or needed +- Switch your image to `lscr.io/linuxserver/nextcloud:version-27.0.0` and start the container. Note the `updater.phar` is no longer available, or needed - Execute `docker logs nextcloud` and check for any issues (report [issues on GitHub](https://github.com/linuxserver/docker-nextcloud/issues)) - As of posting this information, Nextclouod 27 is the latest current version. If you are reading this after a new major version of Nextcloud beyond 27 is released, check [releases on GitHub](https://github.com/linuxserver/docker-nextcloud/releases) and proceed to switch to the next major version tag one by one until you are current. Updating more than one major version at a time is not supported - You should now be able to switch your image to `lscr.io/linuxserver/nextcloud` (no tag) if you prefer to run the latest image (although we do recommend pinning a specific version) From 34384fd8f8c48ffe44c606982ba5df75a46851f3 Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Sat, 24 Jun 2023 07:44:55 -0500 Subject: [PATCH 08/11] Split image table Signed-off-by: Eric Nemchik --- content/issues/2023-06-23-nextcloud.md | 36 ++++++++++++++++---------- 1 file changed, 22 insertions(+), 14 deletions(-) diff --git a/content/issues/2023-06-23-nextcloud.md b/content/issues/2023-06-23-nextcloud.md index 02552046..8cc0afd9 100644 --- a/content/issues/2023-06-23-nextcloud.md +++ b/content/issues/2023-06-23-nextcloud.md @@ -1,12 +1,13 @@ --- -title: 'Notification: Changes to our Nextcloud image' -date: '2023-06-23 22:00:00Z' +title: "Notification: Changes to our Nextcloud image" +date: "2023-06-23 22:00:00Z" informational: true affected: - - 'Notifications' - - 'nextcloud' + - "Notifications" + - "nextcloud" section: issue --- + We are releasing a new version of our [Nextcloud image](https://github.com/linuxserver/docker-nextcloud/) that is built with the Nextcloud application inside the image, rather than in the user `/config` volume. This means manually updating Nextcloud via command line will no longer be necessary or supported. The `updater.phar` command is completely removed. Installations for existing users will be migrated automatically when updating the container image. All future updates to your Nextcloud instance will happen via container image updates. **Updating via the admin web UI is no longer supported.** @@ -33,19 +34,26 @@ If after updating your container image you receive a message along these lines: The version of Nextcloud that you have installed in your persistent `/config` volume will need to be updated using an older image before you can use the new image. -| Image/Tag | PHP | Notes | -| - | - | - | -| `lscr.io/linuxserver/nextcloud:version-26.0.2` | 8.2 | Use this tag if your major version is 26 | -| `lscr.io/linuxserver/nextcloud:26.0.2-ls245` | 8.1 | Included for reference as the last tag released with PHP 8.1 | -| `lscr.io/linuxserver/nextcloud:version-25.0.4` | 8.1 | | -| `lscr.io/linuxserver/nextcloud:version-24.0.12` | 8.1 | Use this tag if your major version is 24 | -| `lscr.io/linuxserver/nextcloud:24.0.6-ls204` | 7.4 | Included for reference as the last tag released with PHP 7.4 | -| `lscr.io/linuxserver/nextcloud:version-23.0.4` | 7.4 | | -| `lscr.io/linuxserver/nextcloud:version-22.2.3` | 7.4 | | +Major version images, to be used for upgrading: + +| Image/Tag | PHP | +| ----------------------------------------------- | --- | +| `lscr.io/linuxserver/nextcloud:version-26.0.2` | 8.2 | +| `lscr.io/linuxserver/nextcloud:version-25.0.4` | 8.1 | +| `lscr.io/linuxserver/nextcloud:version-24.0.12` | 8.1 | +| `lscr.io/linuxserver/nextcloud:version-23.0.4` | 7.4 | +| `lscr.io/linuxserver/nextcloud:version-22.2.3` | 7.4 | + +Package locked tags, listed for LSIO team reference: + +| Image/Tag | PHP | Notes | +| -------------------------------------------- | --- | --------------------- | +| `lscr.io/linuxserver/nextcloud:26.0.2-ls245` | 8.1 | Last tag with PHP 8.1 | +| `lscr.io/linuxserver/nextcloud:24.0.6-ls204` | 7.4 | Last tag with PHP 7.4 | - Check your `/config/www/nextcloud/config/config.php` file or `/config/www/nextcloud/version.php` file to determine the version you have installed - Switch your image to the corresponding major version from the table above (ex: your files indicate `24.x.x`, use `lscr.io/linuxserver/nextcloud:version-24.0.12`) and start the container -- Execute `docker exec -it nextcloud updater.phar` ***repeatedly*** until there are no more updates, or the updater says `This version of Nextcloud is not compatible with > PHP x.x` +- Execute `docker exec -it nextcloud updater.phar` **_repeatedly_** until you have updated to Nextcloud `27.x.x`, or the updater says `This version of Nextcloud is not compatible with > PHP x.x` - Check your files again to determine the version you have installed - If your installed version is below 26, repeat the steps above until you get to version 26 - If your installed version is 26 or 27, continue with the instructions below From d96e779f2e25560a2f9796ff09171f8c214cc7b2 Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Sat, 24 Jun 2023 07:45:25 -0500 Subject: [PATCH 09/11] Update date Signed-off-by: Eric Nemchik --- .../issues/{2023-06-23-nextcloud.md => 2023-06-24-nextcloud.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename content/issues/{2023-06-23-nextcloud.md => 2023-06-24-nextcloud.md} (99%) diff --git a/content/issues/2023-06-23-nextcloud.md b/content/issues/2023-06-24-nextcloud.md similarity index 99% rename from content/issues/2023-06-23-nextcloud.md rename to content/issues/2023-06-24-nextcloud.md index 8cc0afd9..9b71484f 100644 --- a/content/issues/2023-06-23-nextcloud.md +++ b/content/issues/2023-06-24-nextcloud.md @@ -1,6 +1,6 @@ --- title: "Notification: Changes to our Nextcloud image" -date: "2023-06-23 22:00:00Z" +date: "2023-06-24 22:00:00Z" informational: true affected: - "Notifications" From 5db86cad02a06c4daf9c4545e8aa40069608a9ce Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Sat, 24 Jun 2023 10:04:41 -0500 Subject: [PATCH 10/11] Fix tag pin recommendation Add restart step Replace execute with run (wording) Signed-off-by: Eric Nemchik --- content/issues/2023-06-24-nextcloud.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/content/issues/2023-06-24-nextcloud.md b/content/issues/2023-06-24-nextcloud.md index 9b71484f..79dde593 100644 --- a/content/issues/2023-06-24-nextcloud.md +++ b/content/issues/2023-06-24-nextcloud.md @@ -14,7 +14,7 @@ We are releasing a new version of our [Nextcloud image](https://github.com/linux **Downgrading is not supported.** -An important thing to keep in mind is that systems that automatically update your container will result in irreversible changes to your Nextcloud instance. We recommend pinning a specific tagged version like `lscr.io/linuxserver/nextcloud:27.0.0` and manually changing your image version when you are ready to upgrade. +An important thing to keep in mind is that systems that automatically update your container will result in irreversible changes to your Nextcloud instance. We recommend pinning a specific tagged version like `lscr.io/linuxserver/nextcloud:version-27.0.0` and manually changing your image version when you are ready to upgrade. Excerpts from the updated README: @@ -53,16 +53,17 @@ Package locked tags, listed for LSIO team reference: - Check your `/config/www/nextcloud/config/config.php` file or `/config/www/nextcloud/version.php` file to determine the version you have installed - Switch your image to the corresponding major version from the table above (ex: your files indicate `24.x.x`, use `lscr.io/linuxserver/nextcloud:version-24.0.12`) and start the container -- Execute `docker exec -it nextcloud updater.phar` **_repeatedly_** until you have updated to Nextcloud `27.x.x`, or the updater says `This version of Nextcloud is not compatible with > PHP x.x` +- Run `docker exec -it nextcloud updater.phar` **_repeatedly_** until you have updated to Nextcloud `27.x.x`, or the updater says `This version of Nextcloud is not compatible with > PHP x.x` - Check your files again to determine the version you have installed - If your installed version is below 26, repeat the steps above until you get to version 26 - If your installed version is 26 or 27, continue with the instructions below - Switch your image to `lscr.io/linuxserver/nextcloud:version-27.0.0` and start the container. Note the `updater.phar` is no longer available, or needed -- Execute `docker logs nextcloud` and check for any issues (report [issues on GitHub](https://github.com/linuxserver/docker-nextcloud/issues)) +- Run `docker logs nextcloud` and check for any issues (report [issues on GitHub](https://github.com/linuxserver/docker-nextcloud/issues)) - As of posting this information, Nextclouod 27 is the latest current version. If you are reading this after a new major version of Nextcloud beyond 27 is released, check [releases on GitHub](https://github.com/linuxserver/docker-nextcloud/releases) and proceed to switch to the next major version tag one by one until you are current. Updating more than one major version at a time is not supported - You should now be able to switch your image to `lscr.io/linuxserver/nextcloud` (no tag) if you prefer to run the latest image (although we do recommend pinning a specific version) -- Execute `docker exec -it nextcloud mv /config/nginx/site-confs/default.conf /config/nginx/site-confs/default.conf.bak` -- Execute `docker exec -it nextcloud mv /config/nginx/nginx.conf /config/nginx/nginx.conf.bak` +- Run `docker exec -it nextcloud mv /config/nginx/site-confs/default.conf /config/nginx/site-confs/default.conf.bak` +- Run `docker exec -it nextcloud mv /config/nginx/nginx.conf /config/nginx/nginx.conf.bak` +- Run `docker restart nextcloud` - Nextcloud should now be in a working state Optional: From 9dbd66d2d194d52a617d14ca62e5f326854a22ec Mon Sep 17 00:00:00 2001 From: Eric Nemchik Date: Sun, 25 Jun 2023 08:55:17 -0500 Subject: [PATCH 11/11] Update Date Signed-off-by: Eric Nemchik --- .../issues/{2023-06-24-nextcloud.md => 2023-06-25-nextcloud.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename content/issues/{2023-06-24-nextcloud.md => 2023-06-25-nextcloud.md} (99%) diff --git a/content/issues/2023-06-24-nextcloud.md b/content/issues/2023-06-25-nextcloud.md similarity index 99% rename from content/issues/2023-06-24-nextcloud.md rename to content/issues/2023-06-25-nextcloud.md index 79dde593..db6abc10 100644 --- a/content/issues/2023-06-24-nextcloud.md +++ b/content/issues/2023-06-25-nextcloud.md @@ -1,6 +1,6 @@ --- title: "Notification: Changes to our Nextcloud image" -date: "2023-06-24 22:00:00Z" +date: "2023-06-25 22:00:00Z" informational: true affected: - "Notifications"