Can anyone help with testing the update process in NextcloudPi, then report issues to Nextcloud 24 support thread on Github.
Breakage expected!!! Do not test on your actual production instance. Thanks and always keep additional backups!
Is NC24 over ncp-devel available or ist the best way to upgrade manually to NC24?
1 Like
afaik it will all be manual. Expect to be totally on your own. 
found tonight some time to test. But was interrupted by this feedback from the update-page.
“[ nc-update-nextcloud ] (Thu May 5 22:22:14 CEST 2022)
Malformed version 24”
I tested “24” and “24.0” and "24rc2. Is theres something I am missing?
It would be the full number. Documentation here [HowTo] Update NextcloudPi to the latest version
24.0.0
24.0.0rc3
1 Like
NC24 is running on the test-vm without issues.
Will test further and check if something occures.
2 Likes
Upgrade of NCP within docker.
Current Nextcloud version 23.0.6.1
Available Nextcloud version 24.0.2
Download Nextcloud 24.0.2...
Back up current instance...
check free space...
Maintenance mode enabled
backup database...
backup files...
backup /var/www//nextcloud-bkp_20220701_1656698709.tar.gz generated
Maintenance mode disabled
Install Nextcloud 24.0.2...
Restore data...
Fix permissions...
Upgrade...
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Turned on maintenance mode
Updating database schema
Updated database
Disabled incompatible app: calendar
Disabled incompatible app: contacts
Disabled incompatible app: news
Disabled incompatible app: nextcloudpi
Disabled incompatible app: notes
Disabled incompatible app: notify_push
Disabled incompatible app: previewgenerator
Disabled incompatible app: tasks
Updating <federation> ...
Updated <federation> to 1.14.0
Updating <lookup_server_connector> ...
Updated <lookup_server_connector> to 1.12.0
Updating <oauth2> ...
Updated <oauth2> to 1.12.0
Updating <password_policy> ...
Updated <password_policy> to 1.14.0
Updating <files> ...
Updated <files> to 1.19.0
Updating <activity> ...
Updated <activity> to 2.16.0
Updating <circles> ...
Updated <circles> to 24.0.0
Updating <cloud_federation_api> ...
Updated <cloud_federation_api> to 1.7.0
Updating <dav> ...
Fix broken values of calendar objects
Done
0/0 [->--------------------------] 0%
Clean up old calendar subscriptions from deleted users that were not cleaned-up
Done
0/0 [----->----------------------] 0%
Updated <dav> to 1.22.0
Updating <files_sharing> ...
Updated <files_sharing> to 1.16.2
Updating <files_trashbin> ...
Updated <files_trashbin> to 1.14.0
Updating <files_versions> ...
Updated <files_versions> to 1.17.0
Updating <sharebymail> ...
Updated <sharebymail> to 1.14.0
Updating <workflowengine> ...
Updated <workflowengine> to 2.6.0
Updating <comments> ...
Updated <comments> to 1.14.0
Updating <firstrunwizard> ...
Updated <firstrunwizard> to 2.13.0
Updating <nextcloud_announcements> ...
Updated <nextcloud_announcements> to 1.13.0
Updating <notifications> ...
Updated <notifications> to 2.12.0
Updating <systemtags> ...
Updated <systemtags> to 1.14.0
Updating <theming> ...
Updated <theming> to 1.15.0
Updating <accessibility> ...
Migrate old user config
Done
1/1 [============================] 100%
Updated <accessibility> to 1.10.0
Updating <contactsinteraction> ...
Updated <contactsinteraction> to 1.5.0
Updating <dashboard> ...
Updated <dashboard> to 7.4.0
Updating <federatedfilesharing> ...
Updated <federatedfilesharing> to 1.14.0
Updating <files_pdfviewer> ...
Updated <files_pdfviewer> to 2.5.0
Updating <files_rightclick> ...
Updated <files_rightclick> to 1.3.0
Updating <files_videoplayer> ...
Updated <files_videoplayer> to 1.13.0
Updating <logreader> ...
Updated <logreader> to 2.9.0
Updating <photos> ...
Updated <photos> to 1.6.0
Updating <privacy> ...
Updated <privacy> to 1.8.0
Updating <provisioning_api> ...
Updated <provisioning_api> to 1.14.0
Updating <recommendations> ...
Updated <recommendations> to 1.3.0
Updating <serverinfo> ...
Updated <serverinfo> to 1.14.0
Updating <settings> ...
Updated <settings> to 1.6.0
Updating <support> ...
Updated <support> to 1.7.0
Updating <survey_client> ...
Updated <survey_client> to 1.12.0
Updating <text> ...
Updated <text> to 3.5.1
Updating <twofactor_backupcodes> ...
Updated <twofactor_backupcodes> to 1.13.0
Updating <user_status> ...
Updated <user_status> to 1.4.0
Updating <viewer> ...
Updated <viewer> to 1.8.0
Updating <weather_status> ...
Updated <weather_status> to 1.4.0
Starting code integrity check...
Finished code integrity check
Update successful
Turned off maintenance mode
Resetting log level
Check indices of the share table.
Check indices of the filecache table.
Check indices of the twofactor_providers table.
Check indices of the login_flow_v2 table.
Check indices of the whats_new table.
Check indices of the cards table.
Check indices of the cards_properties table.
Check indices of the calendarobjects_props table.
Check indices of the schedulingobjects table.
Check indices of the oc_properties table.
Check indices of the oc_jobs table.
Check indices of the oc_direct_edit table.
Adding direct_edit_timestamp index to the oc_direct_edit table, this can take some time...
oc_direct_edit table updated successfully.
Check columns of the comments table.
Done.
Check primary keys.
Done.
All tables already up to date!
Backup stored at /data/nextcloud/data/ncp-update-backups/nextcloud-bkp_20220701_1656698709-23.0.6.1.tar.gz
Clean up...
Any additional information necessary?
I’m testing Nextcloud 24.0.2 on my Raspberry Pi 4 and it’s running without any problems for about ten days now.
The reason for docker is to upgrade by pulling a more recent Docker image of NextcloudPi, which hasn’t been released yet. Hopefully it will be out soon, but you should never need to upgrade within the container as you normally would in Nextcloud.
You mean for every minor update of NC I should pull a new image? Or just for the major releases?
It is your choice, but the actual idea of Docker is to use it directly for updates. Whether you follow that is up to you. ncp has never been good about minor releases to Docker, but then again the point of NextcloudPi is to only release when fully tested.
How you handle it is up to you. Cheers.
Perhaps a bit off topic, but does this also apply to OS updates, not upgrades? Because that would mean a lot of image and container work for the user as well as the image creator. Thus I applied a hybrid approach and update the docker image only for major changes either in Nextcloud or the OS release.
Other than that you hit the spot. NCP became very slow on minor updates and I am afraid that is not because of a planned testing phase/process or assesment whether the minor releases do not contain security fixes but simply because nobody has more time to spend on the changes.
And of course, if you want users to test updates before you release new images, somebody has to update without having new images available.
1 Like