feat: change database default to mariadb:10.11, fixes #5797

[rfay]

The Issue

• Update mariadb default to current LTS 10.11 in DDEV v1.23.0 #5797

How This PR Solves The Issue

Changes the default. Tries to catch up on some test items that seem to have been neglected.

Manual Testing Instructions

In an empty directory, ddev config --auto && ddev start. ddev describe should show it running mariadb:10.11

Automated Testing Overview

Related Issue Link(s)

Release/Deployment Notes

[github-actions]

Download the artifacts for this pull request:

• all-ddev-executables.zip
• ddev-linux-amd64.zip
• ddev-linux-arm64.zip
• ddev-macos-amd64.zip
• ddev-macos-arm64.zip
• ddev-windows-amd64-installer.zip

See Testing a PR

[rfay]

This has implications for 'latest' docs, but they're not too big. It says 10.11 is default.

[rfay]

It's worth looking a a couple of things here:

• Why wasn't mariadb 10.11 previously being tested when snapshots and export-db were tested (export-db wasn't testing bzip2 on mariadb 10.11 for sure)?
• Are there build complaints in several of the image builds? (Could be spun off into another issue). I know I saw one that has the complaint about where the keys are kept.

[rfay]

mariadb:10.4 failure seems to happen only on certain macOS systems.

I'm able to recreate this, mariadb:10.4 only, on arm64. Maybe it's just arm64 that's the problem. Suspecting bad image push.

2024-02-16 17:40:46 0 [Note] InnoDB: Cannot open '/var/lib/mysql/ib_buffer_pool' for reading: No such file or directory
2024-02-16 17:40:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-02-16 17:40:46 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2024-02-16 17:40:46 0 [ERROR] Failed to initialize plugins.
2024-02-16 17:40:46 0 [ERROR] Aborting

Stack Overflow says this may be out-of-memory, but I doubt it. Another almost certainly unrelated: https://stackoverflow.com/questions/34198735/could-not-open-mysql-plugin-table-some-plugins-may-be-not-loaded

[rfay]

I re-pushed from arm64 machine and it solved this.

make PUSH=true DOCKER_ARGS=--no-cache VERSION=20240213_mariadb_1011_default mariadb_10.4

I will look at the original push (done via github) to see if there are any clues there.

[rfay]

The last docker build here was done in https://github.com/rfay/ddev/actions/runs/7909096636/job/21589704201

It failed mariadb:10.8 and 10.11, didn't understand why, and pushed those from arm64 mac.

I don't see anything at all interesting reviewing the 10.4 build there.

I'll bet this would have failed the CircleCI arm64 build if we had it still enabled for PRs

[rfay]

Why wasn't mariadb 10.11 previously being tested when snapshots and export-db were tested (export-db wasn't testing bzip2 on mariadb 10.11 for sure)?

TestDdevExportDB currently only tests the current default MariaDB version, no others.
TestCmdExportDB also tests only with MariaDB and only with current default
TestDdevAllDatabases test all the right permutations except Postgres:9, which can't properly be done. But it doesn't do bzip2 exports or imports.

[rfay]

Are there build complaints in several of the image builds?

I see this in images based on Ubuntu 22.04: "Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).", but they're in the context of us using apt-key to remove expired keys:

RUN for item in "75DD C3C4 A499 F1A1 8CB5 F3C8 CBF8 D6FD 518E 17E1" "126C 0D24 BD8A 2942 CC7D F8AC 7638 D044 2B90 D010" "D211 6914 1CEC D440 F2EB 8DDA 9D6D 8F6B C857 C906" "A1BD 8E9D 78F7 FE5C 3E65 D8AF 8B48 AD62 4692 5553" "ED6D 6527 1AAC F0FF 15D1 2303 6FB2 A1C2 65FF B764"; do apt-key remove "${item}" || true; done;

I don't think we have to worry about that problem, although we do have to figure out how to stop using apt-key for testing expiration in general, but that should be captured in

• Container test for expiring Debian package keys no longer works (apt-key), monitor debian repositories and keys #5829

[rfay]

The problem pushing images with Ubuntu 22.04-derived dbimages (mariadb:10.8 + mariadb:10.11) is a SEGV on libc-bin (https://github.com/rfay/ddev/actions/runs/7944511561/job/21690113653#step:7:1533)

#16 71.57 Processing triggers for libc-bin (2.35-0ubuntu3.6) ...
#16 71.74 Segmentation fault (core dumped)
#16 71.87 Segmentation fault (core dumped)
#16 71.88 dpkg: error processing package libc-bin (--configure):
#16 71.88  installed libc-bin package post-installation script subprocess returned error exit status 139
#16 71.89 Errors were encountered while processing:
#16 71.89  libc-bin
#16 71.98 E: Sub-process /usr/bin/dpkg returned an error code (1)
#16 ERROR: process "/bin/bash -c apt-get -qq update && DEBIAN_FRONTEND=noninteractive apt-get install -y -o Dpkg::Options::=\"--force-confold\" bzip2 curl gnupg2 less lsb-release pv tzdata vim wget" did not complete successfully: exit code: 100

[rfay]

f3d0804 seems to solve the push problem

[stasadev]

I don't know what the difference is, but the two files are named incorrectly.