I cannot find a way in Unraid to roll back the container. I have always simply updated using community apps and there is no way to select which container to use. I will try the updater.phar when I get home. Thanks
Should give some hints about how to use an older image in unraid.
I’m currently running the update via cli (literally just enter updater.phar in the unraid docker terminal) and it looks promising.
— Edit:
negative, after the updater has done its work, I’m left with the same message: Should the "occ upgrade" command be executed? [Y/n] Y This version of Nextcloud is not compatible with > PHP 8.0.<br/>You are currently running 8.1.16. Keep maintenance mode active? [y/N]
Same thing after container restart…
I noticed that my container version should be around 25 but the updater.phar only mentions 23.0.12.
I guess that means I need to go back to that version?
I switched to image 24.0.2 but it could just have been that I did not exit maintenance mode (which I only noticed after switching, because this brought me php < 8.0
I can now run updater.phar to get to 24.0.9 and then I guess I can update to 25. and use the latest image again.
— last edit:
Yes, that worked! I suppose it might also be possible to use the updater.phar repeatedly with the 25. image, just don’t forget to disable maintance mode again ( occ maintance:mode --off )
I also added the occ upgrade that was suggested by the updater, but I guess the new image would bring those updated apps anyways?
Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done
Start update? [y/N] y
Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.
[] Check for expected files
[] Check for write permissions
[] Create backup
[] Downloading
[] Verify integrity
[] Extracting
[] Enable maintenance mode
[] Replace entry points
[] Delete old files
[] Move new files in place
[] Done
Update of code successful.
Should the “occ upgrade” command be executed? [Y/n] Y
This version of Nextcloud is not compatible with > PHP 8.0. You are currently running 8.1.16.
Keep maintenance mode active? [y/N] N
This version of Nextcloud is not compatible with > PHP 8.0. You are currently running 8.1.16.
Maintenance mode is disabled
I have tried a multitude of things and have no luck. I removed Nextcloud and reinstalled. I now get the following error when launching the html interface: Composer autoloader not found, unable to continue. Check the folder “3rdparty”. Running “git submodule update --init” will initialize the git submodule that handles the subfolder “3rdparty”.
Not sure what happened on the last update but everything appears to be messed up now.
My log file is this. I do see an error for config.php but unsure how to fix this:
text error warn system array login
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service 00-legacy: starting
s6-rc: info: service 00-legacy successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/01-envfile
cont-init: info: /etc/cont-init.d/01-envfile exited 0
cont-init: info: running /etc/cont-init.d/10-adduser
cont-init: info: /etc/cont-init.d/10-adduser exited 0
cont-init: info: running /etc/cont-init.d/20-config
cont-init: info: /etc/cont-init.d/20-config exited 0
cont-init: info: running /etc/cont-init.d/30-keygen
cont-init: info: /etc/cont-init.d/30-keygen exited 0
cont-init: info: running /etc/cont-init.d/40-config
cont-init: info: /etc/cont-init.d/40-config exited 0
cont-init: info: running /etc/cont-init.d/50-install
cont-init: info: /etc/cont-init.d/50-install exited 0
cont-init: info: running /etc/cont-init.d/60-memcache
cp: cannot create regular file ‘/config/www/nextcloud/config/config.php’: No such file or directory
chown: cannot access ‘/config/www/nextcloud/config/config.php’: No such file or directory
cont-init: info: /etc/cont-init.d/60-memcache exited 1
cont-init: info: running /etc/cont-init.d/70-aliases
cont-init: info: /etc/cont-init.d/70-aliases exited 0
cont-init: info: running /etc/cont-init.d/99-custom-files
cont-init: info: /etc/cont-init.d/99-custom-files exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-mods: starting
s6-rc: info: service init-mods successfully started
s6-rc: info: service init-mods-package-install: starting
s6-rc: info: service init-mods-package-install successfully started
s6-rc: info: service init-mods-end: starting
s6-rc: info: service init-mods-end successfully started
s6-rc: info: service init-services: starting
s6-rc: info: service init-services successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun cron (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun php-fpm (no readiness notification)
s6-rc: info: service legacy-services successfully started
s6-rc: info: service 99-ci-service-check: starting
s6-rc: info: service 99-ci-service-check successfully started
[custom-init] No custom services found, skipping…
Just open a terminal and follow the steps.
I got stuck with 2 versions at step 3 or 4 (downloading).
I just moved the updater folder to the root of the container (opening a console from the container):
mv data/updater-oc* ../DELETEME-updater
Then executed again from the main unraid terminal console:
docker exec -it nextcloud updater.phar
Once you get to the last version and the updater did its thing, don’t forget to answer “N” to the last question to get out of the maintenance mode.
I just tried doing a fresh install this morning and was able to actually get to the setup screen. Was having issues connecting to Mariadb. I am going to try installing everything new when I am able to escape work. No idea what changed to enable me to get to the make admin account page but progress has been made.
So I started having issues with other containers and Unraid started telling me the appdata folder was getting marked as read only. After some troubleshooting, it appears that the docker image was corrupt. Now the fun of setting some of these containers back up. Thanks for the help everyone.
Mine did.
For anyone stumbling on this:
The download can take a while depending on available bandwidth on your side as well as on the side of the download location.
It CAN take longer than an hour, even two.
So be patient, I’d start worrying after three hours - then it might be a good idea to cancel an take further steps.
I have to say that I really don’t get why there is no progress bar, which would ease the mind tremendously!