The Basics
- Nextcloud Server version (e.g., 29.x.x):
- Nextcloud Hub 26 Winter (33.0.0) All-In-One Nextcloud AIO v12.9.2
- Operating system and version (e.g., Ubuntu 24.04):
- openSUSE Leap 16.0
- Web server and version (e.g, Apache 2.4.25):
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO - see below
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
Version
Nextcloud Hub 26 Winter (33.0.0)
Update
A new version is available: Nextcloud 33.0.3
1 app has no compatible version for this Nextcloud version available.
Apps missing compatible version
Nextcloud All-in-One
Steps to replicate it:
-
So, in an attempt to always be able to run the latest Nextcloud instance, I tweaked the startcommand provided in https://hub.docker.com/r/nextcloud/all-in-one and GitHub - nextcloud/all-in-one: š¦ The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance. Ā· GitHub (under 3). Assuming that whenever a new mastercontainer becomes available, it will be pulled before docker starts.
-
cat ~/bin/start_nc.sh
#!/bin/bash # For Linux and without a web server or reverse proxy already in place: cNCc="$( sudo docker ps -a | grep aio-mastercontainer | cut -f 1 -d ' ' )" sudo docker stop $(docker ps -a -q) #sudo docker stop ${cNCc} sudo docker rm ${cNCc} #sudo docker rm $(docker ps -a -q) sudo docker pull ghcr.io/nextcloud-releases/all-in-one:latest sudo docker run --env NEXTCLOUD_MOUNT="/cloud_folder/" \ --env NEXTCLOUD_DATADIR="/cloud_folder" \ --init --sig-proxy=false --name nextcloud-aio-mastercontainer \ --restart always --publish 80:80 --publish 8080:8080 --publish 8443:8443 \ --security-opt label:disable \ --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \ --volume /var/run/docker.sock:/var/run/docker.sock:ro \ -d ghcr.io/nextcloud-releases/all-in-one:latest -
After this startup, I can go to the AIO page on my http://[IP_ADDRESS_HERE]:8080/containers and start the containers
-
It looks as if there is no update in the all-in-one release where my AIO instance does detect a new version should be availableā¦
Expected Finding
I assume that an AIO instance will only report a new version is available, when it is also installable - that is when a new AIO mastercontainer is available for download.
For now, I think the only way to resolve this, is to wait until a new mastercontainer is published?