Mariadb on arm still v10.1

It seems like the mariadb container for arm is still running v10.1. When runningdocker run --rm linuxserver/mariadb:110.4.11mariabionic-ls47 the output is the following:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing... 
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing... 
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    911
User gid:    911
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
[cont-init.d] 30-config: exited 0.
[cont-init.d] 40-initialise-db: executing... 
Setting Up Initial Databases
Installing MariaDB/MySQL system tables in '/config/databases' ...
2020-01-03 16:25:20 3069811520 [Note] /usr/sbin/mysqld (mysqld 10.1.43-MariaDB-0ubuntu0.18.04.1) starting as process 275 ...
OK
Filling help tables...
2020-01-03 16:25:29 3069819712 [Note] /usr/sbin/mysqld (mysqld 10.1.43-MariaDB-0ubuntu0.18.04.1) starting as process 304 ...
OK
Creating OpenGIS required SP-s...
2020-01-03 16:25:32 3069745984 [Note] /usr/sbin/mysqld (mysqld 10.1.43-MariaDB-0ubuntu0.18.04.1) starting as process 334 ...
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following commands:

'/usr/bin/mysqladmin' -u root password 'new-password'
'/usr/bin/mysqladmin' -u root -h 6928b62359ef password 'new-password'

Alternatively you can run:
'/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.

See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.

You can start the MariaDB daemon with:
cd '/usr' ; /usr/bin/mysqld_safe --datadir='/config/databases'

You can test the MariaDB daemon with mysql-test-run.pl
cd '/usr/mysql-test' ; perl mysql-test-run.pl

Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/

2020-01-03 16:25:35 3069623104 [Note] mysqld (mysqld 10.1.43-MariaDB-0ubuntu0.18.04.1) starting as process 362 ...
Database Setup Completed



#################################################################
# No root password or too short a password ,min of 4 characters #
# No root password will be set, this is not a good thing        #
# You shoud set one after initialisation with the command       #
#          mysqladmin -u root password <PASSWORD>               #
#################################################################


[cont-init.d] 40-initialise-db: exited 0.
[cont-init.d] 99-custom-scripts: executing... 
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
200103 16:25:46 mysqld_safe Logging to syslog.
200103 16:25:46 mysqld_safe Starting mysqld daemon with databases from /config/databases
^CCaught SIGTERM signal!
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Running the same command on x86 shows the version being 10.4

That’s because the official mariadb repo only provides packages for x86_64 and aarch64, no armhf. Armhf one gets pulled from the ubuntu bionic repo, which is a little behind

Ok, thank you for clarifying.

Wow, took me a while to get to this page and realise it’s not me. Tried everything to get Mariadb to 10.4, but it kept starting 10.1. Trying to get wiki.js up and running, which uses json column types, which need MariaDB 10.2 or higher. Any idea when this will be updated, or can you point me to the repo so I can keep an eye on it? Thanks!

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