Let’s try running the updater from the command line and see what happens?
Just make sure that www-data is the correct user, as it may be different on your system.
with docker you are not expected to run an updater… you should wait until the desired version is available (latest 22.2 is based on 22.2.3) and then update your container…
I’m not sure how portainer works. Nextcloud keeps using same version tag for long time - maybe portainer doesn’t recognize there is new image… so please check how/if there is a way to force refresh of the container… but in general the process is the same: docker container must be updated by running new image and not through internal updater…
Select Containers, then stop the container that you’d like to update.
Select the container, and you’ll see a button named Recreate. By selecting this button, the container will take the persistent data and recreate the container. Keep in mind that the only data that will stay on the container is data that was mapped to a volume. This is explained in greater detail in the video above.
Select Pull latest image, then Recreate.
When this process is finished, the container will be recreated with the latest image. Select the container and Start it. The status will change to running.