The repository is forked from mysql by Docker team. INIT_ROCKSDB – Set to 1 to allow the container to be started with enabled ROCKSDB storage engine.INIT_TOKUDB – Set to 1 to allow the container to be started with enabled TOKUDB storage engine.The images recognize two additional environment variables for TokuDB and RocksDB for MySQL (available since v5.6): You can easily switch between MySQL and Percona Server images, provided you are running on the compatible version. In a way, you can think of it as an improved version of Oracle’s MySQL. Percona Server for MySQL comes with XtraDB storage engine (a drop-in replacement for InnoDB) and follows the upstream Oracle MySQL releases very closely (including all the bug fixes in it) with some additional features like MyRocks storage engine, TokuDB as well as Percona’s own bug fixes. The code repository points out that first commit was with 15 actively contributors mostly from Percona development team. Percona only maintains the latest 3 major MySQL versions for container images – 5.6, 5.7 and 8.0. It supports both x86 and x86_64 architecture and the image is based on CentOS 7. These are the only official Percona Server Docker images, created and maintained by the Percona team. Percona Server is a fork of MySQL created by Percona. If you would like to set up a more advanced MariaDB setup (replication, Galera, sharding), there are other images built to achieve that objective much more easily, e.g, bitnami/mariadb as explained further down. Mixing or switching between MariaDB and MySQL in a cluster is not recommended. Simply said, that once you are in the MariaDB ecosystem, you probably have to stick with it. However, there are ways to migrate between each other by using logical backup. In terms of database architecture design, some MariaDB versions are not 100% compatible and no longer a drop-in replacement with theirs respective MySQL versions. MariaDB server used to be a fork of MySQL but now it has been diverted away from it. Most applications that required MySQL as the database backend is commonly compatible with MariaDB, since both are talking the same protocol. This image serves as a general-purpose image and follows the instructions, environment variables and configuration file structure as mysql (Docker). It uses the same style of building structure as the mysql (Docker) image, but it comes with multiple architectures support:Īt the time of this writing, the images support MariaDB version 5.5 up until 10.4, where image with the “latest” tag size is around 120MB. The images are maintained by Docker community with the help of MariaDB team. If your application requires the latest MySQL database container, this is the most recommended public image you can use. The image size (tag: latest) is averagely small (129MB), easy to use, well maintained and updated regularly by the maintainer. The following environment variables are available on most of the MySQL container images on Docker Hub: MariaDB, Percona and MySQL Server (Oracle) images are following a similar environment variables, configuration file structure and container initialization process flow. Most of the MySQL images built by others are inspired by the way this image was built. ![]() At this time of writing, all the MySQL major versions are supported – 5.5, 5.6, 5.7 and 8.0 on x86_64 architecture only. It supports the Docker version down to 1.6 on a best-effort basis. It has been forked ~1300 times with 18 active contributors. It can be considered the most popular publicly available MySQL server images hosted on Docker Hub and one of the earliest on the market (the first commit was May 18, 2014). ![]() The images are built and maintained by the Docker community with the help of MySQL team. The following table summarizes the different options: Aspect The listing here is based on the result of Docker Hub, the world’s largest library and community for container images. Some of them include non-essential MySQL-related applications, while others just serve as a plain mysqld instance. The images we have chosen are general-purpose public images that can at least run a MySQL service. In this blog post, we are going to look at some of the most popular Docker images to run our MySQL or MariaDB server. Check out this blog post if you want to learn how to build and publish your own Docker image for MySQL, or this blog post if you just want to learn the basics of running MySQL on Docker. A good (and popular) container image must have well-written documentation with clear explanations, an actively maintained repository and with regular updates. That is why there are many similar images being built by the community, with minor differences but really serving a common purpose. A Docker image can be built by anyone who has the ability to write a script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |