cimg/mysql Docker镜像基于官方MySQL稳定版构建,为开发与CI/CD环境提供轻量级高性能服务。内置优化配置,支持数据持久化与网络隔离,基于Ubuntu系统并包含常用客户端工具。可快速部署单节点实例及容器化架构集成,适合自动化测试、本地开发及小型生产环境。镜像定期更新,确保安全性与兼容性,简化数据库环境一致性管理。
</p> <h1>CircleCI Convenience Images => MySQL</h1> <h3>A Continuous Integration focused MySQL Docker image built to run on CircleCI</h3>
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.
Support Policy
The CircleCI Docker Convenience Image support policy can be found on the https://circleci.com/docs/convenience-images-support-policy 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:
yamljobs: build: docker: - image: cimg/go:1.17 - image: cimg/mysql:8.0 steps: - checkout
In 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.
How This Image Works
This image contains the MySQL database and its complete toolchain.
RAM
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.
Tagging Scheme
This image has the following tagging scheme:
cimg/mysql:<mysql-version>
<mysql-version> - The version of MySQL 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:
bashgit 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:
bashgit remote add upstream https://github.com/CircleCI-Public/cimg-mysql.git
Cloning For Maintainers ( you have write access to this repository)
Clone the project with the following command so that you populate the submodule:
bashgit clone --recurse-submodules git@github.com:CircleCI-Public/cimg-mysql.git
Generating Dockerfiles
Dockerfiles 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:
bash./shared/gen-dockerfiles.sh 8.0
The generated Dockerfile will be located at ./8.0/Dockefile.
To build this image locally and try it out, you can run the following:
bashdocker build -t test/mysql:8.0 -f 8.0/Dockerfile . docker run -it test/mysql:8.0 bash
Building the Dockerfiles
To build the Docker images locally as this repository does, you'll want to run the build-images.sh script:
bash./build-images.sh
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 MySQL version of v9.99, you would run the following from the repo root:
bash./shared/release.sh 9.99
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 https://github.com/CircleCI-Public/cimg-shared.
For those changes to affect this image, the submodule needs to be updated.
Typically like this:
bashcd 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).
Contributing
We encourage https://github.com/CircleCI-Public/cimg-mysql/issues and https://github.com/CircleCI-Public/cimg-mysql/pulls 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
https://circleci.com/docs/ - The official CircleCI Documentation website.
https://circleci.com/docs/2.0/configuration-reference/#section=configuration - 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.
https://docs.docker.com/ - 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.
镜像拉取方式
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。
DockerHub 原生拉取命令
用户好评
来自真实用户的反馈,见证轩辕镜像的优质服务