Last changed
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpMySQL is a widely used open-source relational database management system.
Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.
This image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard registry.
The default MySQL port is 3306
. To run a quick test MySQL server container with an empty root password, use the following command:
Don't forget to replace {YOUR-PRIVATE-REPO} with your organization's designated private repository.
After the server is up and running, you can connect to it using the mysql
client. This is available for most Linux-based systems in a package called mysql-client
, in case you don't have it installed yet. To connect to the server as root
and without a password, use the following command:
Please note this only works because the server was initialized with the option MYSQL_ALLOW_EMPTY_PASSWORD
, which should never be used on production environments.
Following that, you should now see the MySQL prompt:
You can now create databases, users, and tables as you would with a regular MySQL server. To exit the client, run the exit
command on the MySQL prompt. To stop the server, press Ctrl+C
in the terminal where Docker is running. The container will stop and be removed automatically.
You can use environment variables to set up your database upon initialization. The following variables are available for this purpose:
MYSQL_ROOT_HOST
: This variable allows you to specify the host from which the root user can connect. The default value is localhost
.MYSQL_ROOT_PASSWORD
: Sets the password for MySQL's root superuser account.MYSQL_RANDOM_ROOT_PASSWORD
: When this variable is set, a random password is generated for the root superuser account. This password is printed to stdout at the end of the container initialization process.MYSQL_ALLOW_EMPTY_PASSWORD
: This variable allows you to run the MySQL container with an empty root password. This is insecure and should only be used for tests and local development.MYSQL_DATABASE
: Creates a new database upon initialization.MYSQL_USER
: Together with MYSQL_PASSWORD
, this environment variable can be used to create a new database user and grant them full access to the database defined by MYSQL_DATABASE
.MYSQL_PASSWORD
: This should be used in conjunction with the MYSQL_USER
environment variable to set up the database user's password.Another feature from the MySQL initialization script allows you to import an SQL file via a volume mounted to /docker-entrypoint-initdb.d
. For example, if you have a my-data.sql
file in your current folder, you can run the following command to have this data automatically imported to your database:
To facilitate testing the various environment variables and options when initializing your MySQL server, you can use a Docker Compose setup like the following. Again, remember to replace {YOUR-PRIVATE-REPO}
with your organization's designated private repository.
Save this file as docker-compose.yaml
and run docker-compose up
in the same directory. Once the server is up and running, you can connect via the mysql
client with the following command:
This docker-compose.yaml
sets up a MySQL database with a default database and user. Other services can be added to create a local multi-node environment for development and tests. You can iterate on this setup to test different configurations and scenarios.
If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.
Chainguard Images are a collection of container images designed for security and minimalism.
Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.
The main features of Chainguard Images include:
-dev
VariantsAs mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev
variant which does include a shell and package manager.
Although the -dev
image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev
variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.
That being said, it’s worth noting that -dev
variants of Chainguard Images are completely fine to run in production environments. After all, the -dev
variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.
To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
Apache-2.0
Artistic-1.0-Perl
BSD-3-Clause
CC-PDDC
GCC-exception-3.1
GPL-1.0-or-later
GPL-2.0-only
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement