Nextcloud 30 drops 32 bit support? (no MariaDB 10.5 support)

ℹ️ Support
1

Quick question: does NC v30 really need MariaDB v10.6? Would it be dangerous to run NC v30 with MariaDB 10.5?

(in detail: not aware of the specific reasons why support for v10.5 has been dropped with NC v30)

According to Upgrade to Nextcloud 30 — Nextcloud latest Administration Manual latest documentation it dropped support for v10.5.

For some OS, 10.5 is the latest available version. And if you are running a 32 bit OS on an armhf architecture, there are no newer versions. Even the official MariaDB packages at Index of /repo/10.6/debian/ don’t provide one for armhf.

That way, even System requirements — Nextcloud latest Administration Manual latest documentation still states…

A 64-bit CPU, OS and PHP is required for Nextcloud to run well.
32-bit systems are supported, with the following known limitations:
- Dates before Unix Epoch (1970-01-01) are not supported
- Dates after 2038 are not supported

…now more or less…

…is not valid anymore.

NC v30 → MariaDB 10.6 → not available, so NC v29 is the latest usable version with 32 bit OS. Stuck. At least that’s valid for my current setup.

Unfortunately Update on 32-bit support: decision to block the update on Nextcloud 26 reverted is locked meanwhile (since 12 days, wow what a great timing :-)).

For me this means the remaining time where NC v29 is still supported (2025-04 according to Maintenance and Release Schedule · nextcloud/server Wiki · GitHub) needs to be used to upgrade (reinstall) OS, MariaDB etc.

Next to the initial question from the beginning this topic might help other users running older 32 bit based OS.

2

According to MariaDB - Wikipedia 10.5 is EOL at June 2025.
Doesn’t that fit to NC29?

3

You guess that rough date alignment (2 months mismatch according to my calender :slight_smile: ) is the reason, so no technical ones?

Does not really answer

4

Does it really matter? I mean, they didn’t test NC30 against versions <10.6, which means no one can guarantee that it’ll still work fine with 10.5, which would be reason enough for me not to use it anymore.

Also, in addition to any compatibility issues that may arise, you’re exposing yourself to potential security risks after MariaDB 10.5 goes EOL in June.

I know people don’t like to hear this, but maybe it’s time to upgrade to newer hardware, because 32-bit is definitely on its way out, and the longer you wait, the more problems you’re going to run into, MariaDB/Nextcloud being just the first of many to come.

5

It’s unsupported/untested. Dangerous depends on your definition I guess.

For some OS, 10.5 is the latest available version. And if you are running a 32 bit OS on an armhf architecture, there are no newer versions.

That’s not true. e.g. Debian ships MariaDB 10.11 in Bookworm for armhf.

Even the official MariaDB packages at Index of /repo/10.6/debian/ don’t provide one for armhf.

MariaDB has never published official builds for arm32/armv7/armhf. That’s always come from the downstream packages like Debian, Ubuntu, etc. So you’ll have 32-bit support within MariaDB as long as your OS distribution continues to build and support it.

So I don’t see the problem.

Also, there are other databases supported by Nextcloud Server anyhow.

1 Like
6

As mentioned, I am well aware of all of this, just being interested in the inner mechanics what leads to drop support for certain component versions.

For me personally new hardware has just been ordered.

My intention for this topic was to send out a note to all the other 32 bit users that despite the official statement to continue support 32 bit, NC 30 (or EOL of NC 29) might mark a deadline for others. Clock is ticking, loudly.

1 Like
7

See GitHub - nextcloud/docker-ci: 📦 Containers used for Continous Integration jobs (automated testing) for all testing repos and actions.