openstack-mariadb-oshelm

packaged by Chainguard

Chainguard Container for openstack-mariadb-oshelm

MariaDB server with the Python tooling used by the OpenStack-Helm mariadb chart, compatible with the upstream openstack-helm-images mariadb image.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/openstack-mariadb-oshelm:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This image is a drop-in replacement for the OpenStack-Helm quay.io/airshipit/mariadb image (latest-ubuntu_noble, MariaDB 11.4). Like upstream, it combines the MariaDB 11.4 server and client with the Python modules (pymysql, kubernetes, pykube-ng and iso8601) that the OpenStack-Helm mariadb chart's server start and mariadb_controller scripts import. Those scripts are mounted from the chart's ConfigMaps at runtime and are not baked into the image.

The Galera 4 wsrep provider is installed at /usr/lib/galera/libgalera_smm.so, the path the chart sets in wsrep_provider, and mariadb-backup and socat are included for the chart's wsrep_sst_method=mariabackup state transfers.

Differences from the upstream image:

• The image runs directly as the non-root mysql user (UID/GID 999, the same IDs as upstream and the chart's runAsUser: 999) instead of starting as root and dropping privileges with gosu. gosu is not included.
• The image is built on Chainguard OS packages rather than Ubuntu, and has no package manager.
• MariaDB uses its default configuration paths (/etc/my.cnf, /etc/mysql/my.cnf, ~/.my.cnf) without the Debian conf.d include.
• /usr/local/bin/healthcheck.sh from the upstream image is not included, so healthcheck.sh --connect health checks do not work; use mariadb-admin ping instead.
• rsync is not included, so wsrep_sst_method=rsync does not work; use the chart's default mariabackup method.

A FIPS variant is available as openstack-mariadb-oshelm-fips.

Getting Started

The entrypoint is docker-entrypoint.sh and the default command is mariadbd, matching upstream. The default MariaDB port is 3306.

docker run -d --name mariadb -p 3306:3306 \
  -e MARIADB_ROOT_PASSWORD=secret \
  cgr.dev/ORGANIZATION/openstack-mariadb-oshelm:latest

Connect with the bundled client:

docker exec -it mariadb mariadb -uroot -psecret -e "SELECT VERSION();"

Check the Python tooling used by the chart:

docker run --rm --entrypoint python3 cgr.dev/ORGANIZATION/openstack-mariadb-oshelm:latest \
  -c "import pymysql, kubernetes, pykube, iso8601; print(pymysql.__version__, kubernetes.__version__)"

Deploying with OpenStack-Helm

Point every image slot the chart runs from this image at it, and give the chart registry credentials for cgr.dev (a pull token). The chart attaches imagePullSecrets to its pods only when endpoints.oci_image_registry.auth.enabled is set. Create an override file:

cat > mariadb-images.yaml <<EOF
endpoints:
  oci_image_registry:
    auth:
      enabled: true
      mariadb:
        username: <pull-token-username>
        password: <pull-token-password>
    host_fqdn_override:
      default: cgr.dev
images:
  tags:
    mariadb: cgr.dev/ORGANIZATION/openstack-mariadb-oshelm:latest
    mariadb_controller: cgr.dev/ORGANIZATION/openstack-mariadb-oshelm:latest
    mariadb_db_controller: cgr.dev/ORGANIZATION/openstack-mariadb-oshelm:latest
    scripted_test: cgr.dev/ORGANIZATION/openstack-mariadb-oshelm:latest
pod:
  replicas:
    server: 1
EOF
helm repo add openstack-helm https://tarballs.opendev.org/openstack/openstack-helm
helm install mariadb openstack-helm/mariadb --namespace openstack --create-namespace \
  --values mariadb-images.yaml

Configuration

The image supports the standard MariaDB entrypoint environment variables, such as MARIADB_ROOT_PASSWORD, MARIADB_RANDOM_ROOT_PASSWORD, MARIADB_ALLOW_EMPTY_ROOT_PASSWORD, MARIADB_DATABASE, MARIADB_USER and MARIADB_PASSWORD. LANG is set to C.UTF-8, as upstream.

Exposed ports

• 3306/tcp: MariaDB client connections.

Volumes

• /var/lib/mysql: the MariaDB data directory. Mounted volumes must be writable by UID 999 (mysql).

Documentation and Resources

• OpenStack-Helm images
• OpenStack-Helm mariadb chart
• MariaDB documentation

The upstream image definitions are licensed under the Apache License 2.0.

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.