Docker Library: 12.3 release based on ubuntu26.04

[grooverdan]

12.3 isn't currently GA.

Its release date is after the 12.3 release
https://jira.mariadb.org/projects/MDEV?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased

So lets use the latest LTS Ubuntu for this.

Requires Docker Library PR MariaDB/mariadb-docker#683 to be merged soon after deployment.

[RazvanLiviuVarzaru]

@grooverdan I have a question please, just for my knowledge,
is MariaDB/mariadb-docker#683 a hard dependency?

I was trying to understand how amd64-rhel8-dockerlibrary is affecting https://github.com/MariaDB/mariadb-docker/actions/workflows/ci.yml but I see that the produced quay.io images are not used at any step in the latter.

I only had arrived to this conclusion, correct me if I am wrong:
The scope of amd64-rhel8-dockerlibrary is to simulate what GitHub CI will do, offering us an early validation that the container images are OK before a MariaDB Server official release and before an official Docker Library release. The latter depends on an official MariaDB Server release because the in-container installation is performed from mirror.mariadb.org

OK means: images built, tested via docker-library-test.sh and the external operator workflow is green.

If the above is correct this means: MariaDB/mariadb-docker#683 can only be merged if the updated amd64-rhel8-dockerlibrary is green for >= 12.3 release candidates?

[RazvanLiviuVarzaru]

The buildbot changes LGTM!
I am afraid this will require a Buildbot restart, because utils.py was changed but
I can schedule a release for next week since I need to deploy some C/ODBC changes.

You can merge this one.
Thanks!

[grooverdan]

@grooverdan I have a question please, just for my knowledge, is MariaDB/mariadb-docker#683 a hard dependency?

Without it being merged at the time the dockerlibrary worker is triggered on a 12.3+ release, the FROM ubuntu:noble will still be there and it will attempt to install MariaDB packages from Ubuntu 26.04. There is a small window of aligned ABI version dependences where this might work.

I was trying to understand how amd64-rhel8-dockerlibrary is affecting https://github.com/MariaDB/mariadb-docker/actions/workflows/ci.yml

It doesn't.

but I see that the produced quay.io images are not used at any step in the latter.

workflow is against MariaDB operator only and unit tests only.

I only had arrived to this conclusion, correct me if I am wrong: _The scope of amd64-rhel8-dockerlibrary is to simulate what GitHub CI will do,

offering us an early validation that the container images are OK before a MariaDB Server official release and before an official Docker Library release. The latter depends on an official MariaDB Server release because the in-container installation is performed from mirror.mariadb.org_

OK means: images built, tested via docker-library-test.sh and the external operator workflow is green.

If the above is correct this means: MariaDB/mariadb-docker#683 can only be merged if the updated amd64-rhel8-dockerlibrary is green for >= 12.3 release candidates?

https://doi-janky.infosiftr.net/job/put-shared/job/light/job/mariadb/ (or a similar build) is the Docker Official Images of MariaDB. The GH workflows aren't important.

These are build from a ref hash on release - https://github.com/docker-library/official-images/pulls?q=is%3Apr+label%3Alibrary%2Fmariadb+is%3Aclosed

github workflow on the master branch is a reflection and sanity test of what happens before a PR to DOI.

The github master branch is what release versions of MariaDB have been tested/released. Should an out-of-band release happen, it can happen straight on the master branch.

The github next branch is mean to be a working version of what will what will happen next release. It includes features of the container, and the integration with the server.

github workflow on the next branch, recently reinstated, also checks against archive.mariadb,org, the last release. This is currently incorrect, its building against archive.mariadb.org, which is why its failing on the 12.3+ branch(es). It should be building on the repo files of https://ci.mariadb.org/ like what BB does. The workflow is to check that container changes aren't causing a regression.

The BB is a check that server changes are still compatible with the Docker Official Image, and to generate an image used by quay.io/mariadb-foundation/mariadb-devel.