-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust postgres image refs in examples to a well supported version #1764
Comments
there used to be some issue with 10.6 #1492 , so it tagged for fixed version |
Hi @MegadoomerX - No. They're just examples. It takes a lot of work keeping them all up-to-date. It's also expected that those using them educate themselves on Docker basics and some thought into their environment's specific requirements. There's only so much we can do. :-) That said, this is a community project so you're welcome to submit PRs to try to clean some of them up a bit. |
We should probably just lock all the |
MariaDB was changed to a LTS tag since they introduces STS versions. PostgreSQL does not have any STS versions and the latest version of Nextcloud usually supports all maintained releases. |
The latest postgres (17) isn't officially supported in any currently supported version of Nextcloud Server. The other reason to lock things, perhaps more important and which is unique to postgres, is that the there is no "simple upgrade path" for their image between major versions. See docker-library/postgres#37 For #2310 I picked v15 because it's the highest in-common across Nc v28-v30. |
TBH, I think it's just a question of updating the documentation for it. |
I find it curious that the Docker Compose examples contain a fixed version tag for MariaDB (
mariadb:10.5
) while a rolling release tag was chosen for the PostgreSQL container (postgres:alpine
).This is especially strange to me, as MariaDB is developed to be mostly cross-compatible in versions while PostgreSQL needs a manual database dump and rebuild on every major update. Also, the current MariaDB version 10.5 is out of date (currently 10.8.3 is the latest release).
Is there any reasoning for this that I'm unaware of?
The text was updated successfully, but these errors were encountered: