Hi,
I want to deploy Nextcloud version 31.0.9 specifically using Docker, but when I use ghcr.io/nextcloud-releases/all-in-one:latest it always installs the latest Nextcloud version, which I want to avoid. I do not want automatic upgrades and need a fixed version (31.0.9). Is it possible to run an exact Nextcloud version with Nextcloud AIO, or does AIO always track the latest release? If AIO does not support this, what is the recommended Docker-based way to deploy and keep Nextcloud pinned to version 31.0.9?
Some quick off the top of my head thoughts:
You could pull it off with AIO by tracking down the image that still defaults to deploying v31.0.9 (or building it yourself - it’s release v11.10.0), but the problem is that the way that AIO works it would eventually not be possible to update the installation if you’re planning to keep in frozen at 31.0.9 for more than a few months (well, it is often is but requires a bunch of manual effort) . AIO isn’t really designed to operate that way.
The most “supported” way would be to use the Docker micro-services image. Each image tag there is locked to a specific version, so it’s easy to deploy a specific version. However that image isn’t the same animal as AIO; it’s heavily used but not a turnkey stack.
1 Like