It was a "very fresh" install. The old containers plus the corresponding folders were deleted first. Yesterday I made an even more radical fresh installation: Same effects. I repeated the remedies described in RE: Do you have an old version of 32-bit arm OVM? and my nextcloud on Helios4 runs satisfactorly.
However, since this is no longer supported software, it may not be worth researching further.
While migrating from armhf or a fresh install?
It was a fresh install. Therefore I was so surprised that an important tool (auth_pam_tool) and a necessary file (mariadb-bin.index) was not accessible or present.
32bit support for my Helios4 is not a matter generally today, Armbian and OMV support the platform as long as only the NAS functionality is concerned. Another point of view is docker support for 32bit. That's the background of my plan
> And I'll start developing a migration path to 64-bit, perhaps leaving the Helios4 for a while as a pure NAS, i.e. no docker support at all.
As a pure NAS the system is unavailable from the internet by a specific VPN connection only.
btw No 1: After nextcloud 26.0.2 was running finally, the system was upgraded successfully twice to 26.0.3 and 27.0.
btw No 2: I worked in IT security for almost 20 years, most of that time at a large telco. If I'll experience the slightest indication of a security vulnerability the system will go offline if the vulnerability can't be mitigated. Regular security scans, e.g. https://scan.nextcloud.com/ will be performed. Today's rating: A.
OTOH: In general I support your suggestion.
Thank you. I'll give it a try at next opportunity. I'll report.
"Next opportunity" was today. My experiences:
chown: cannot access '/auth_pam_tool_dir': No such file or directory
Cannot change ownership of the '/auth_pam_tool_dir' directory to the 'abc' user.
Check that you have the necessary permissions and try again.
I know my actions look as severe hacks and I'm not happy with them. And I can't anticipate possible nasty adverse effects. I'm open to repeat the mariadb part of the nextcloud armhf installation.
And I'll start developing a migration path to 64-bit, perhaps leaving the Helios4 for a while as a pure NAS, i.e. no docker support at all. Parallely building a 64-bit OMV with nextcloud first, moving the RAID5 at a later time.
Display MoreNextcloud latest version using armhf was v26.0.2-ls246
SWAG latest version using armhf was v2.6.0-ls212
mariaDB latest version using armhf was v10.6.13-r0-ls97
Above that, armhf was deprecated.
If you want to continue using the latest supported armhf version, those tags need to be added on the YML in order to make the containers binded to those versions.:
Codeservices: mariadb: # image: lscr.io/linuxserver/mariadb:latest image: lscr.io/linuxserver/mariadb:10.6.13-r0-ls97 swag: image: lscr.io/linuxserver/swag:2.6.0-ls212 nextcloud: image: lscr.io/linuxserver/nextcloud:26.0.2-ls246
Thank you. I'll give it a try at next opportunity. I'll report.
The time to move to arm64 is NOW (in this case). And I can see this happening to a huge amount of users that run armhf systems with Linuxserver images.
For Nextcloud transition from armhf to arm64, I don't know if it will be just a matter of recreating the container on a new arm64 system.
Maybe something to ask on their GitHub.
I really like my Helios4 so I try to postpone switching to a new hardware until it gets completely unavoidable. Helios4 is a supported Armbian platform.
I just found rather new "arm32v7-latest" packages on https://github.com/linuxserver/docker-nextcloud, https://github.com/linuxserver/docker-mariadb, https://github.com/linuxserver/docker-swag. Perhaps macom (author of the corresponding How-To) can comment. I could live with a fresh install of nextcloud because I'm the sole user.
Do you have an old version of 32-bit arm OVM?
Yes I do. And it causes more and more problems for me. I'm using a Helios4 (see e.g. "My NAS the Helios4" by HyronHelper). Please do not misunderstand: Everything I projected is up and running including NAS, docker, Nextcloud, ..., but the future is very uncertain. The biggest problem is linuxserver/nextcloud which doesn't support armhf any more.
Display MoreWIth armbian, since there's no grub, adding to armbianEnv.txt
extraargs=apparmor=0
and rebooting worked on my Rock64 without having to downgrade. Would imaging should also work on Odroid HC-2, XU4, etc.
Updating grub worked on my other OMV systems with x86 processors.
Works for me. Simple but effective solution on my armbian (32-bit) Helios4.
I'm back in business after going back to "image: webhippie/mariadb:latest-arm32v6" and a restore of the last but one backup.
I had to go this way because I didn't succeed with the latest mariadb image from webhippie which is release 10.6. I found several links where an incompatibility between nextcloud and mariadb 10.6 are described, e.g. https://github.com/nextcloud/docker/issues/1492
I'll stay for a while with mariadb:latest-arm32v6 until the incompatibility will be resolved, instead of to try the workaround mentioned in the line above.
EDIT:
linuxserver/mariadb is at 10.5 → No incompatibility
Googling brings up this: https://til.codes/how-to-fix-e…ed-storage-engine-innodb/
Be sure to take backups before changing anything
Last night I found a similar link. But I had no success (I better should have mention this detail).
The log says now:
2021-09-28 8:43:44 0 [ERROR] InnoDB: Page [page id: space=0, page number=342] log sequence number 3501945904 is in the future! Current system log sequence number 144932.
2021-09-28 8:43:44 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
<<<< many times repeated >>>>
2021-09-28 8:43:44 0 [Note] InnoDB: 128 rollback segments are active.
2021-09-28 8:43:44 0 [ERROR] InnoDB: Page [page id: space=0, page number=607] log sequence number 2377389283 is in the future! Current system log sequence number 144932.
2021-09-28 8:43:44 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-09-28 8:43:44 0 [ERROR] InnoDB: Page [page id: space=0, page number=610] log sequence number 2377408309 is in the future! Current system log sequence number 144932.
2021-09-28 8:43:44 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-09-28 8:43:44 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-09-28 8:43:44 0 [Note] InnoDB: Setting file '/var/lib/mysql/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-09-28 8:43:44 0 [Note] InnoDB: File '/var/lib/mysql/ibtmp1' size is now 12 MB.
2021-09-28 8:43:44 0 [Note] InnoDB: 10.6.4 started; log sequence number 144920; transaction id 16869309
2021-09-28 8:43:44 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-09-28 8:43:44 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2021-09-28 8:43:44 0 [ERROR] InnoDB: Page [page id: space=0, page number=1] log sequence number 269474793 is in the future! Current system log sequence number 144932.
2021-09-28 8:43:44 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
<<<< last two log items many times repeated >>>>
2021-09-28 8:43:44 0 [Note] Server socket created on IP: '0.0.0.0'.
2021-09-28 8:43:44 0 [ERROR] InnoDB: Page [page id: space=0, page number=1] log sequence number 269474793 is in the future! Current system log sequence number 144932.
2021-09-28 8:43:44 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
<<<< last two log items many times repeated >>>>
2021-09-28 8:43:44 0 [Note] InnoDB: Buffer pool(s) load completed at 210928 8:43:44
2021-09-28 8:43:44 0 [ERROR] Incorrect definition of table mysql.event: expected column 'definer' at position 3 to have type varchar(, found type char(141).
2021-09-28 8:43:44 0 [ERROR] mysqld: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2021-09-28 8:43:44 0 [Note] mysqld: ready for connections.
Version: '10.6.4-MariaDB-debug' socket: '/tmp/mysqld.sock' port: 3306 MariaDB ServerThe nextcloud login screen appears now but after the logon I see the "Internal Server Error" again.
As on a armfh platform (see signature) I had to migrate from linuxserver/mariadb to webhippie/mariadb according to the guide by Morlan. Applying my weekly "docker-compose pull" I got for the first time a (brand-)new version of webhippie/mariadb. But after the "docker-compose up -d" and trying to connect to my nextcloud I get
CodeInternal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log.It looks as if the mariadb-container does not start.
Any clue?
Not without further information. What does the mariadb-container log say?
...
That's the mariadb-log:
2021-09-28 7:20:55 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2021-09-28 7:20:55 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-09-28 7:20:55 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-09-28 7:20:55 0 [ERROR] Aborting
> writing mariadb config
{"level":"debug","time":"2021-09-28T07:20:57Z","msg":"starting gomplate"}
{"level":"debug","version":"3.10.0","build":"e11e134e","time":"2021-09-28T07:20:57Z","msg":"config is:\n---\ninputFiles: [/etc/templates/my.cnf.tmpl]\noutputFiles: [/etc/mysql/my.cnf]\nleftDelim: '{{'\nrightDelim: '}}'\npluginTimeout: 5s\n"}
{"level":"debug","data":"&{ctx:0x27b8810 Sources:map[] sourceReaders:map[] cache:map[] extraHeaders:map[]}","time":"2021-09-28T07:20:57Z","msg":"created data from config"}
{"level":"debug","templatesRendered":1,"errors":0,"duration":0.002828699,"time":"2021-09-28T07:20:57Z","msg":"completed rendering"}
> chown data directory
> starting mariadb service
2021-09-28 7:20:57 0 [Note] mysqld (server 10.6.4-MariaDB-debug) starting as process 7 ...
2021-09-28 7:20:57 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2021-09-28 7:20:57 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-09-28 7:20:57 0 [Note] InnoDB: Number of pools: 1
2021-09-28 7:20:57 0 [Note] InnoDB: Using generic crc32 instructions
2021-09-28 7:20:57 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2021-09-28 7:20:57 0 [Note] InnoDB: Using Linux native AIO
2021-09-28 7:20:57 0 [Note] InnoDB: Initializing buffer pool, total size = 16777216, chunk size = 16777216
2021-09-28 7:20:57 0 [Note] InnoDB: Completed initialization of buffer pool
2021-09-28 7:20:57 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.8.
2021-09-28 7:20:57 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1447] with error Generic error
2021-09-28 7:20:57 0 [Note] InnoDB: Starting shutdown...
2021-09-28 7:20:58 0 [ERROR] Plugin 'InnoDB' init function returned error.
2021-09-28 7:20:58 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2021-09-28 7:20:58 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-09-28 7:20:58 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-09-28 7:20:58 0 [ERROR] Aborting
> writing mariadb config
{"level":"debug","time":"2021-09-28T07:21:00Z","msg":"starting gomplate"}
{"level":"debug","version":"3.10.0","build":"e11e134e","time":"2021-09-28T07:21:00Z","msg":"config is:\n---\ninputFiles: [/etc/templates/my.cnf.tmpl]\noutputFiles: [/etc/mysql/my.cnf]\nleftDelim: '{{'\nrightDelim: '}}'\npluginTimeout: 5s\n"}
{"level":"debug","data":"&{ctx:0x44066c0 Sources:map[] sourceReaders:map[] cache:map[] extraHeaders:map[]}","time":"2021-09-28T07:21:00Z","msg":"created data from config"}
{"level":"debug","templatesRendered":1,"errors":0,"duration":0.003645202,"time":"2021-09-28T07:21:00Z","msg":"completed rendering"}
> chown data directory
> starting mariadb service
2021-09-28 7:21:00 0 [Note] mysqld (server 10.6.4-MariaDB-debug) starting as process 9 ...
2021-09-28 7:21:00 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2021-09-28 7:21:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-09-28 7:21:00 0 [Note] InnoDB: Number of pools: 1
2021-09-28 7:21:00 0 [Note] InnoDB: Using generic crc32 instructions
2021-09-28 7:21:00 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2021-09-28 7:21:00 0 [Note] InnoDB: Using Linux native AIO
2021-09-28 7:21:00 0 [Note] InnoDB: Initializing buffer pool, total size = 16777216, chunk size = 16777216
2021-09-28 7:21:00 0 [Note] InnoDB: Completed initialization of buffer pool
2021-09-28 7:21:00 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.8.
2021-09-28 7:21:00 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1447] with error Generic error
2021-09-28 7:21:00 0 [Note] InnoDB: Starting shutdown...
2021-09-28 7:21:00 0 [ERROR] Plugin 'InnoDB' init function returned error.
2021-09-28 7:21:00 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2021-09-28 7:21:00 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-09-28 7:21:00 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-09-28 7:21:00 0 [ERROR] Aborting
> writing mariadb config
{"level":"debug","time":"2021-09-28T07:21:03Z","msg":"starting gomplate"}
{"level":"debug","version":"3.10.0","build":"e11e134e","time":"2021-09-28T07:21:03Z","msg":"config is:\n---\ninputFiles: [/etc/templates/my.cnf.tmpl]\noutputFiles: [/etc/mysql/my.cnf]\nleftDelim: '{{'\nrightDelim: '}}'\npluginTimeout: 5s\n"}
{"level":"debug","data":"&{ctx:0x2c320f0 Sources:map[] sourceReaders:map[] cache:map[] extraHeaders:map[]}","time":"2021-09-28T07:21:03Z","msg":"created data from config"}
{"level":"debug","templatesRendered":1,"errors":0,"duration":0.002520941,"time":"2021-09-28T07:21:03Z","msg":"completed rendering"}
> chown data directory
> starting mariadb service
2021-09-28 7:21:03 0 [Note] mysqld (server 10.6.4-MariaDB-debug) starting as process 7 ...
2021-09-28 7:21:03 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2021-09-28 7:21:03 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-09-28 7:21:03 0 [Note] InnoDB: Number of pools: 1
2021-09-28 7:21:03 0 [Note] InnoDB: Using generic crc32 instructions
2021-09-28 7:21:03 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2021-09-28 7:21:03 0 [Note] InnoDB: Using Linux native AIO
2021-09-28 7:21:03 0 [Note] InnoDB: Initializing buffer pool, total size = 16777216, chunk size = 16777216
2021-09-28 7:21:03 0 [Note] InnoDB: Completed initialization of buffer pool
2021-09-28 7:21:03 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.8.
2021-09-28 7:21:03 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1447] with error Generic error
2021-09-28 7:21:03 0 [Note] InnoDB: Starting shutdown...
2021-09-28 7:21:04 0 [ERROR] Plugin 'InnoDB' init function returned error.
2021-09-28 7:21:04 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2021-09-28 7:21:04 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-09-28 7:21:04 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-09-28 7:21:04 0 [ERROR] Aborting
> writing mariadb config
{"level":"debug","time":"2021-09-28T07:21:08Z","msg":"starting gomplate"}
{"level":"debug","version":"3.10.0","build":"e11e134e","time":"2021-09-28T07:21:08Z","msg":"config is:\n---\ninputFiles: [/etc/templates/my.cnf.tmpl]\noutputFiles: [/etc/mysql/my.cnf]\nleftDelim: '{{'\nrightDelim: '}}'\npluginTimeout: 5s\n"}
{"level":"debug","data":"&{ctx:0x2fd4600 Sources:map[] sourceReaders:map[] cache:map[] extraHeaders:map[]}","time":"2021-09-28T07:21:08Z","msg":"created data from config"}
{"level":"debug","templatesRendered":1,"errors":0,"duration":0.002613097,"time":"2021-09-28T07:21:08Z","msg":"completed rendering"}
> chown data directory
> starting mariadb service
2021-09-28 7:21:08 0 [Note] mysqld (server 10.6.4-MariaDB-debug) starting as process 9 ...
2021-09-28 7:21:08 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2021-09-28 7:21:08 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-09-28 7:21:08 0 [Note] InnoDB: Number of pools: 1
2021-09-28 7:21:08 0 [Note] InnoDB: Using generic crc32 instructions
2021-09-28 7:21:08 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2021-09-28 7:21:08 0 [Note] InnoDB: Using Linux native AIO
2021-09-28 7:21:08 0 [Note] InnoDB: Initializing buffer pool, total size = 16777216, chunk size = 16777216
2021-09-28 7:21:08 0 [Note] InnoDB: Completed initialization of buffer pool
2021-09-28 7:21:08 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.8.
2021-09-28 7:21:08 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1447] with error Generic error
2021-09-28 7:21:08 0 [Note] InnoDB: Starting shutdown...
2021-09-28 7:21:09 0 [ERROR] Plugin 'InnoDB' init function returned error.
2021-09-28 7:21:09 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2021-09-28 7:21:09 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-09-28 7:21:09 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-09-28 7:21:09 0 [ERROR] AbortingAs on a armfh platform (see signature) I had to migrate from linuxserver/mariadb to webhippie/mariadb according to the guide by Morlan. Applying my weekly "docker-compose pull" I got for the first time a (brand-)new version of webhippie/mariadb. But after the "docker-compose up -d" and trying to connect to my nextcloud I get
Internal Server Error
The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.It looks as if the mariadb-container does not start.
Any clue?
Display MoreThat's a good question
When I was on NC v20, there was a warning on the "Settings-> General View" about the upcoming v21 beeing incompatible with mariaDB 10.1 (which is used in the bionic version of linuxserver).
Maybe it's changed now but I really didn't saw it.
Hence the post on page27 to change the DB to webhippie (mariaDB 10.4)
For new ymls, it's better to apply the tag mariadb:alpine (mDB 10.5) since it will be used as "latest" soon
The problem with the incompatibility arises on 32-bit platforms as my Helios 4. I moved to webhippie and I'm waiting for the alpine based mariadb will be out of its pre-release state.
As Soma I already enabled 4-Byte support in the past. For the restore of the database I used the "original" script, i.e. not the enhanced command.
Emojis are still fine in nextcloud->mail: Subject and content with emojis are represented correctly. A text file containing emojis looks correct but not in the sidebar but i'm not sure whether this effect is a consequence of the former restore command.
Another topic:
linuxserver/docker-mariadb is migrating away from mariabionic (with 10.1.47) to alpine-10.5.8 (see https://github.com/linuxserver/docker-mariadb/releases).
Morlan
I'm stuck at last step (Disable maintenance mode)
See my comments inline.
Display MoreFredK Here's the guide. I hope I didn't forget a step...
....
Before "docker-compose up -d" I inserted a "docker-compose pull"
- Start containers: docker-compose up -d
....
In the next command I changed "oc_admin@%;" to "oc_admin'@'%'"
- GRANT ALL PRIVILEGES ON nextcloud.* TO oc_admin@%;
...
- Disable maintenance mode of nextcloud docker: docker exec nextcloud sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off
I got an exception.
root@helios4:/home/docker1/nextcloud# docker exec nextcloud sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off
An unhandled exception has been thrown:
Doctrine\DBAL\DBALException: Failed to connect to the database: An exception occurred in driver: SQLSTATE[HY000] [1045] Access denied for user 'oc_he'@'nextcloud.nextcloud_default' (using password: YES) in /config/www/nextcloud/lib/private/DB/Connection.php:72
Stack trace:
#0 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(1449): OC\DB\Connection->connect()
#1 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(892): Doctrine\DBAL\Connection->getWrappedConnection()
....
Could it be that I created nextcloud in the past as my unprivileged user "he"?
EDIT:
After repeating the database command using oc_he instead of oc_admin disabling maintenance mode was successful.
Nextcloud started, login successful!
Thank you Morlan. Tomorrow I'll give it a try. Fingers already crossed.
Then maybe I'd better postpone the migration of the mariadb docker provider, but at the latest by the time nextcloud 21 is available for my HW platform.
hey,
maybe that will help you DB Backup & Restore
in the last post you will find the scripts - was designed for backups so it should work.
Thank you. Tomorrow is the day ...
...This would mean that you perform a sql dump of your nextcloud database (activate nextcloud maintenance before exporting and also take a backup) and import it into the new MariaDB. Are you able to do that?
A few details would be gratefully accepted.
Let me come back to my question in #446.
In nextcloud now 20.0.7 I get the following warning in Settings->Overview:
QuoteMariaDB version "10.1.47-MariaDB-0ubuntu0.18.04.1" is used. Nextcloud 21 will no longer support this version and requires MariaDB 10.2 or higher.
My hardware (see signature) is an arm32 device.
Even the newest mariadb image https://github.com/linuxserver…/110.4.17mariabionic-ls10 ("Bump to 10.4 ...") doesn't suppress the warning message.
Why? "Inside" the nextclouddb (=mariadb) container we have 10.1.47:
root@7f6f464c863c:~# apt list --installed | grep maria
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
mariadb-client-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local]
mariadb-client-core-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local]
mariadb-common/now 1:10.1.47-0ubuntu0.18.04.1 all [installed,local]
mariadb-server/now 1:10.1.47-0ubuntu0.18.04.1 all [installed,local]
mariadb-server-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local]
mariadb-server-core-10.1/now 1:10.1.47-0ubuntu0.18.04.1 armhf [installed,local]What can I do?
Remark: I also started a corresponding thread in armbian forum:
https://forum.armbian.com/topi…iadb-docker-version-102ff
EDIT:
In https://discourse.linuxserver.io I found two posts which bring some light into the topic.
1. From Nov 2020: https://discourse.linuxserver.…adb-on-raspberry-pi3/2221
Mariadb dont push newer binaries for armhf
2. From Mar 2020: https://discourse.linuxserver.…db-on-arm-still-v10-1/944
arm one pulls from the ubuntu bionic repo: https://packages.ubuntu.com/bionic-updates/mariadb-server
either that will be updated, or we’ll update the baseimage to ubuntu focal after it is released
And the problem is: ubuntu focal doesn't support 32bit. So what to do with nextcloud 21?