Installation of system tables failed about docker-mariadb

[semyonsh]

This is still an issue on Raspbian 10 and ARMv7 with the latest image.

I can't replicate this. Raspbian 10 on armv7 (Pi 4b) using the compose from the original post and it starts as expected.

You're correct, my apologies.

In all the troubles getting it to work I didn't pay enough attention to the most obvious error message:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Your DockerHost is most likely running an outdated version of libseccomp

To fix this, please visit https://docs.linuxserver.io/faq#libseccomp

Some apps might not behave correctly without this

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Followed the instructions at mentioned link and updated libseccomp:

wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1_armhf.deb
dpkg -i libseccomp2_2.5.1-1_armhf.deb

Container started working after restart/redeploy with compose. Can't reproduce the error anymore.

Hope this helps anyone who also doesn't read properly :)

[stoinov]

from the upstream issue it seems that the last usable version for arm64 seems to be 10.4.13. Confirming that tag 110.4.13mariabionic-ls76 works on my device.
We will be waiting for a permanent resolution by the MariaDB team.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the issue template!

[billbrod]

This happens with both the latest image and arm32v7-110.4.14mariabionic-ls77

[aptalca]

Try it with an empty config folder (or better yet, remove the mountpoint altogether) and see if it starts up

[billbrod]

Nope, same error regardless of whether the config folder is populated, empty, or removed.

[billbrod]

I was unable to find a solution for this, but I was trying to use this with the LinuxServer Nextcloud image, and I was able to get the official postgres image working as a backend instead.

[d-d]

A workaround for this is to create the config directory manually before starting the container

mkdir config
chmod 755 config
docker-compose up -d

The reported error seems to have a root cause that the /config directory is not created and needs to have write permissions.

The 10-adduser script does chown of directories not yet created until 30-config
40-initialise_db once again does chown -R but not until the end of the script

The config directory is missing, an error is thrown at docker-compose up, since it's not created until 30-config

When attempting to use UMASK=0046 in the docker-compose.yml to get working permissions I discovered a related problem.

The image seems to be forcing UMASK to 0640. I am not sure why this is forced... but it seems wrong, they perhaps intended 640 to be the permissions and not the mask.

[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
UMASK corrected from 0046 to 0646 ...
201003 12:03:43 mysqld_safe Logging to syslog.

The correction logic comes from /usr/bin/mariadbd-multi

if (defined($ENV{UMASK})) {
  my $UMASK = $ENV{UMASK};
  my $m;
  my $fmode = "0640";

  if(($UMASK =~ m/[^0246]/) || ($UMASK =~ m/^[^0]/) || (length($UMASK) != 4)) {
    printf("UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.\n");
    printf("The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.\n"); }
  else {

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[semyonsh]

This is still an issue on Raspbian 10 and ARMv7 with the latest image.

[thespad]

This is still an issue on Raspbian 10 and ARMv7 with the latest image.

I can't replicate this. Raspbian 10 on armv7 (Pi 4b) using the compose from the original post and it starts as expected.

[stoinov]

I have the same issue with using latest linux/arm64/v8 image on Odroid-C2 using DietPi (optimized Debian) as OS.
I don't see the libseccomp error in my logs - just the same thing as in the initial post.

I created the config folder, and put the env file inside. Once ran the container created databases and logs folder and initializes the custom.cnf file. but fails on the next steps.

[thespad]

I have the same issue with using latest linux/arm64/v8 image on Odroid-C2 using DietPi (optimized Debian) as OS. I don't see the libseccomp error in my logs - just the same thing as in the initial post.

I created the config folder, and put the env file inside. Once ran the container created databases and logs folder and initializes the custom.cnf file. but fails on the next steps.

What version of docker are you running?

[stoinov]

Version: 19.03.15

[thespad]

That's your issue. You'll see the same problems as those with the missing libseccomp if you're running Docker versions older than 20.10.0.

[stoinov]

I upgraded my Debian from strech to bullseye and my docker to 20.10.9
I still get the same error when starting the container.

[thespad]

And dpkg -l | grep "libseccomp" shows at least version 2.4.4?

[stoinov]

libseccomp2:arm64 2.5.1-1

[thespad]

Can you try

docker exec mariadb apk -U add libseccomp
docker exec mariadb scmp_sys_resolver faccessat

Assuming your container is called mariadb otherwise change as appropriate.

Post the output to the second command.

[stoinov]

it reported just 48

[thespad]

Oh, made a typo, should be

docker exec mariadb scmp_sys_resolver faccessat2

As per the Alpine 3.14 release notes it should return 439 if everything is correct.

[stoinov]

now it responded with 439 as expected

[stoinov]

I just noticed that the error is different than the original now:
/var/run/s6/etc/cont-init.d/40-initialise-db: line 4: 293 Illegal instruction (core dumped) mysqld --datadir="${DATADIR}" --init-file="${tempSqlFile}" --user=abc

The config folder I am mapping is with 777 permissions and the subfolders still gets created.

[thespad]

Can you provide your full run/compose and the full container logs.

[stoinov]

running the container with: docker run -d --restart unless-stopped --network test --name mariadb -h mariadb -e TZ=Europe/Sofia -e PUID=0 -e PGID=0 -v /mariadb:/config linuxserver/mariadb
the config folder holds an env file with the required properties.

here are the logs:

[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... 
-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/
Brought to you by linuxserver.io
-------------------------------------
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    0
User gid:    0
-------------------------------------
[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' ...
Illegal instruction (core dumped)
Installation of system tables failed!  Examine the logs in
/config/databases for more information.
The problem could be conflicting information in an external
my.cnf files. You can ignore these by doing:
    shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf
You can also try to start the mysqld daemon with:
    shell> /usr/bin/mysqld --skip-grant-tables --general-log &
and use the command line tool /usr/bin/mysql
to connect to the mysql database and look at the grant tables:
    shell> /usr/bin/mysql -u root mysql
    mysql> show tables;
Try 'mysqld --help' if you have problems with paths.  Using
--general-log gives you a log in /config/databases that may be helpful.
The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
You can find the latest source at https://downloads.mariadb.org and
the maria-discuss email list at https://launchpad.net/~maria-discuss
Please check all of the above before submitting a bug report
at https://mariadb.org/jira
/var/run/s6/etc/cont-init.d/40-initialise-db: line 4:   294 Illegal instruction     (core dumped) mysqld --datadir="${DATADIR}" --init-file="${tempSqlFile}" --user=abc

[thespad]

Don't run with PUID and/or PGID set to root, it's not a supported configuration.

[stoinov]

I have 4 other containers from linuxserver that run with root just fine.
I tested with both PUID and PGID 1000 but the outcome is the same - folders get created the error is illegal instruction

[thespad]

I didn't say it'll never work, I said it was an unsupported configuration. Is 1000 the UID/GID of a value user on the host?

What do the logs in /config/databases say?

[stoinov]

there is a user with that ID on the host.
There are no logs in the /config/databases folder. The only file created is a default configuration.

[stoinov]

I've been having issues with the official MariaDB image too and we got some more details over in their issue. You can check it out to see if it helps.
Also I went ahead and tested running the container without mapping external folders, which should rule out any permissions issues I assume. The result was the same error.