New Service – quay.io/mariadb-foundation/mariadb-devel
During the development of MariaDB, a lot of things are tested. However the most important workload to be tested is the one we don’t have access to, and that is your workload.
As many of you run your own CI, we’d like you to invite you to join the testing of MariaDB. quay.io/mariadb-foundation/mariadb-devel is a container repository using the latest from our main stable branches. By the time any code gets into these branches it has been reviewed and passed our tests. The developers of the change consider it finished, so this is the perfect time to take this code and test it on your workload.
To make this easier, the quay.io/mariadb-foundation/mariadb-devel is functionally identical to the Docker Library mariadb container (docker.io/library/mariadb). All interactions are the same. The differences that you’ll notice are:
- Its based on the very latest MariaDB versions and the latest Dockerfile and entrypoint from https://github.com/MariaDB/mariadb-docker.
- There are unreleased version released.
- Container logs have a message “Starting MariaDB 11.3.2-MariaDB-1:11.3.2+maria~ubu2204 source revision 068a6819eb63bcb01fdfa037c9bf3bf63c33ee42” so that if you report a bug, quote the source revision we’ll know what exact version you problem is occurring at.
- There are only the tags of the major versions and they will frequently change.
- There are some preview release tags that will be announced separately.
- The apt repo in the container is a temporary location only.
Tags that are available in addition to major/minor version tags are:
- quay.io/mariadb-foundation/mariadb-devel:verylatest (beta/rc)
- quay.io/mariadb-foundation/mariadb-devel:latest (stable)
- quay.io/mariadb-foundation/mariadb-devel:latest-lts (stable and long term maintained)
- quay.io/mariadb-foundation/mariadb-devel:ealiest-lts (earliest long term maintained)
- quay.io/mariadb-foundation/mariadb-devel:ealiest (earliest maintained version)
If you encounter a problem in these containers please do create a MariaDB JIRA bug report with the details. There’s a good chance important and regression bugs found will be corrected before a formal release.
For anyone who can’t remember all the commands, this worked for me (just replace ‘podman’ with ‘docker’ if you prefer, and you need to run as root/sudo privs unless you have enabled rootless mode which is easier in podman):
# Retrieve the image and create the container:
podman create -p 127.0.0.1:3306:3306 --name mariadb108 -e MARIADB_ROOT_PASSWORD=mypass \
quay.io/mariadb-foundation/mariadb-devel:10.8
# Start the container:
podman start mariadb108
# Enjoy:
mariadb
That last command assumes you have the `mariadb` client installed. It also assumes you have the connection parameters in your `~/.my.cnf` file. Otherwise:
mariadb -uroot -pmypass
If you don’t have the `mariadb` client installed, you can also use the client in the container:
podman exec -it mariadb108 mariadb -uroot -pmypass