cimg/mariadb pulls statistics

CircleCI Convenience Images => MariaDB

A Continuous Integration focused MariaDB Docker image built to run on CircleCI

*This image is designed to supercede the legacy CircleCI MariaDB image, circleci/mariadb.*

cimg/mariadb is a Docker image created by CircleCI with continuous integration builds in mind.

Support Policy

The CircleCI Docker Convenience Image support policy can be found on the CircleCI docs site. This policy outlines the release, update, and deprecation policy for CircleCI Docker Convenience Images.

Table of Contents

• Getting Started • How This Image Works • Development • Contributing • Additional Resources • License

Getting Started

This image can be used with the CircleCI docker executor as a secondary image. For example:

In the above example, the CircleCI Go Docker image is used for the primary container while the MariaDB image is used as a secondary. More specifically, the tag 10.6.4 is used meaning the version of MariaDB will be v10.6.4. You can now connect to a MariaDB instance from the primary image within the steps for this job.

How This Image Works

This image contains the MariaDB database and its complete toolchain.

RAM

The legacy version of this image, circleci/mariadb had a RAM variant. This is no longer the case. We're determining how much of a performance increase does this variant actually give before we decide to bring it back. If you used the legacy MariaDB image and you have data on the ram vs non-ram variant build times, please open a GitHub Issue and let us know.

Tagging Scheme

This image has the following tagging scheme:

- The version of MariaDB to use.

Development

Images can be built and run locally with this repository. This has the following requirements:

• local machine of Linux (Ubuntu tested) or macOS • modern version of Bash (v4+) • modern version of Docker Engine (v19.03+)

Cloning For Community Users (no write access to this repository)

Fork this repository on GitHub. When you get your clone URL, you'll want to add --recurse-submodules to the clone command in order to populate the Git submodule contained in this repo. It would look something like this:

If you missed this step and already cloned, you can just run git submodule update --recursive to populate the submodule. Then you can optionally add this repo as an upstream to your own:

Cloning For Maintainers ( you have write access to this repository)

Clone the project with the following command so that you populate the submodule:

Generating Dockerfiles

Dockerfiles can be generated for a specific MariaDB version using the gen-dockerfiles.sh script. For example, to generate the Dockerfile for v10.6.4, you would run the following from the root of the repo:

The generated Dockerfile will be located at ./10.6.4/Dockefile. To build this image locally and try it out, you can run the following:

Building the Dockerfiles

To build the Docker images locally as this repository does, you'll want to run the build-images.sh script:

This would need to be run after generating the Dockerfiles first. When releasing proper images for CircleCI, this script is run from a CircleCI pipeline and not locally.

Publishing Official Images (for Maintainers only)

The individual scripts (above) can be used to create the correct files for an image, and then added to a new git branch, committed, etc. A release script is included to make this process easier. To make a proper release for this image, let's use the fake MariaDB version of v9.99, you would run the following from the repo root:

This will automatically create a new Git branch, generate the Dockerfile(s), stage the changes, commit them, and push them to GitHub. The commit message will end with the string [release]. This string is used by CircleCI to know when to push images to Docker Hub. All that would need to be done after that is:

• wait for build to pass on CircleCI • review the PR • merge the PR

The main branch build will then publish a release.

Incorporating Changes

How changes are incorporated into this image depends on where they come from.

build scripts - Changes within the ./shared submodule happen in its own repository. For those changes to affect this image, the submodule needs to be updated. Typically like this:

parent image - By design, when changes happen to a parent image, they don't appear in existing MariaDB images. This is to aid in "determinism" and prevent breaking customer builds. New Go images will automatically pick up the changes.

If you *really* want to publish changes from a parent image into the MariaDB image, you have to build a specific image version as if it was a new image. This will create a new Dockerfile and once published, a new image.

MariaDB specific changes - Editing the Dockerfile.template file in this repo will modify the MariaDB image specifically. Don't forget that to see any of these changes locally, the gen-dockerfiles.sh script will need to be run again (see above).

Contributing

We encourage issues and pull requests against this repository.

Please check out our contributing guide which outlines best practices for contributions and what you can expect from the images team at CircleCI.

Additional Resources

CircleCI Docs - The official CircleCI Documentation website. CircleCI Configuration Reference - From CircleCI Docs, the configuration reference page is one of the most useful pages we have. It will list all of the keys and values supported in .circleci/config.yml. Docker Docs - For simple projects this won't be needed but if you want to dive deeper into learning Docker, this is a great resource.

License

This repository is licensed under the MIT license. The license can be found here.

Description from the Docker Hub listing.