Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.6.18
-
None
-
Debian 12 Bookworm
Description
Because of the new mariadb-backup dump format, DDEV needs to install a matching mysql client in its webserver image instead of using the distribution default.
We would do this with the mariadb_repo_setup package, (see docs which call out doing this with 10.6)
ddev-webserver is based on Debian 12 Bookworm. mariadb_repo_setup doesn't work with Debian 12 Bookworm.
This is easy to demonstrate with `docker run -it --rm debian:bookworm bash -c 'apt update && apt install -y curl && curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | bash -s – --mariadb-server-version="mariadb-10.6"'`
The output is
```
- [info] Checking for script prerequisites.
- [error] MariaDB Server version 10.6 is not working.
- Please verify that the version is correct.
- Not all releases of MariaDB are available on all distributions.
# - The latest MariaDB Server versions are:
- 10.4.34 10.5.25 10.6.18 10.11.8 11.0.6 11.1.5 11.2.4 11.4.2 11.5.1
# - More information on MariaDB releases is available at:
- https://mariadb.com/kb/en/release-notes/
```
Related issue where we're working on resolving this for DDEV is at https://github.com/ddev/ddev/issues/6083
Attachments
Issue Links
- is caused by
-
-
- Closed
-
Activity
A given Debian system may want to connect to a mariadb server of a different version. Recent events have made this very painfully true.
Is it reasonable to think that a mariadb-client 10.11 will be able to predictably connect/manage to most mariadb-server versions?
Can't think of a case where it wouldn't.
Sorry I haven't given with ddev as much attention as it deserves. I'll see if I can give it more time next week.
rfay, so what kind of resolution would you expect here?
We generally don't build or provide MariaDB versions earlier than what distribution natively offers.
mariadb-client-10.11 should work with all earlier versions.
Is there anything we can do here?
You can close this, thanks for paying attention.
Assuming that the 10.11 MariaDB clients for Debian 12 Bookworm would be adequate, we implemented them in the ddev-webserver by default.
A writeup on the chaos caused by the new dump format: https://ddev.com/blog/mariadb-dump-breaking-change/
Thanks, that helped. I think we can easily fix this to work with MySQL client (which will bring CVE-2024-21096 back, of course).
Would that be what you need?
new 10.5 release will use MariaDB-only conditional comments, which are ignored by MySQL client.
I'm closing this issue as "Not a Bug" because the originally reported problem — mariadb_repo_setup not offering 10.6 for Bookworm — is indeed not a bug.
The minimum available for bookworm is 10.11, which is what the distro releases https://packages.debian.org/bookworm/mariadb-server
This is done so that from the mariadb repos isn't doing a downgrade.