This image is designed to supercede the legacy CircleCI MySQL image, circleci/mysql.
cimg/mysql is a Docker image created by CircleCI with continuous integration builds in mind.
This image can be used with the CircleCI docker executor as a secondary image.
For example:
jobs:
build:
docker:
- image: cimg/go:1.17
- image: cimg/mysql:8.0
steps:
- checkoutIn the above example, the CircleCI Go Docker image is used for the primary container while the MySQL image is used as a secondary.
More specifically, the tag 8.0 is used meaning the version of MySQL will be v8.0.
You can now connect to a MySQL instance from the primary image within the steps for this job.
This image contains the MySQL database and its complete toolchain.
The legacy version of this image, circleci/mysql 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 MySQL image and you have data on the ram vs non-ram variant build times, please open a GitHub Issue and let us know.
This image has the following tagging scheme:
cimg/mysql:<mysql-version>
<mysql-version> - The version of MySQL to use.
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+)
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:
git clone --recurse-submodules <my-clone-url>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:
git remote add upstream https://github.com/CircleCI-Public/cimg-mysql.gitClone the project with the following command so that you populate the submodule:
git clone --recurse-submodules git@github.com:CircleCI-Public/cimg-mysql.gitDockerfiles can be generated for a specific MySQL version using the gen-dockerfiles.sh script.
For example, to generate the Dockerfile for v8.0, you would run the following from the root of the repo:
./shared/gen-dockerfiles.sh 8.0The generated Dockerfile will be located at ./8.0/Dockefile.
To build this image locally and try it out, you can run the following:
docker build -t test/mysql:8.0 -f 8.0/Dockerfile .
docker run -it test/mysql:8.0 bashTo build the Docker images locally as this repository does, you'll want to run the build-images.sh script:
./build-images.shThis 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.
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 MySQL version of v9.99, you would run the following from the repo root:
./shared/release.sh 9.99This 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.
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:
cd shared
git pull
cd ..
git add shared
git commit -m "Updating submodule for foo."parent image - By design, when changes happen to a parent image, they don't appear in existing MySQL 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 MySQL 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.
MySQL specific changes - Editing the Dockerfile.template file in this repo will modify the MySQL 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).
We encourage issues and pull requests against this repository. In order to value your time, here are some things to consider:
- We won't include just anything in this image. In order for us to add a tool within the MySQL image, it has to be something that is maintained and useful to a large number of MySQL users. Every tool added makes the image larger and slower for all users so being thorough on what goes in the image will benefit everyone.
- PRs are welcome. If you have a PR that will potentially take a large amount of time to make, it will be better to open an issue to discuss it first to make sure it's something worth investing the time in.
- Issues should be used to report bugs or request additional/removal of tools in this image. For help with images, please visit CircleCI Discuss.
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.
This repository is licensed under the MIT license. The license can be found here.