Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-26 23:08:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/mysql] Release 9.6.0-debian-12-r4 (#91774)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-03-21 04:54:34 +01:00
committed by GitHub
parent 8b2ff6dc62
commit 87313aae44
2 changed files with 15 additions and 427 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
bitnami/mysql/9.6/debian-12/Dockerfile
View File

@@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-02-19T03:13:51Z" \
org.opencontainers.image.created="2026-03-21T03:40:17Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/mysql/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/mysql" \
@@ -28,7 +28,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"ini-file-1.4.9-7-linux-${OS_ARCH}-debian-12" \
"ini-file-1.4.9-8-linux-${OS_ARCH}-debian-12" \
"mysql-9.6.0-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
@@ -51,7 +51,7 @@ COPY rootfs /
RUN /opt/bitnami/scripts/mysql/postunpack.sh
ENV APP_VERSION="9.6.0" \
BITNAMI_APP_NAME="mysql" \
IMAGE_REVISION="3" \
IMAGE_REVISION="4" \
PATH="/opt/bitnami/common/bin:/opt/bitnami/mysql/bin:/opt/bitnami/mysql/sbin:$PATH"
EXPOSE 3306

436
bitnami/mysql/README.md
View File

@@ -1,7 +1,5 @@
# Bitnami Secure Image for MySQL
## What is MySQL?
> MySQL is a fast, reliable, scalable, and easy to use open source relational database system. Designed to handle mission-critical, heavy-load production applications.
[Overview of MySQL](https://www.mysql.com)
@@ -66,31 +64,17 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## Using `docker-compose.yaml`
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/mysql).
## Persisting your database
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a directory at the `/bitnami/mysql/data` path. If the mounted directory is empty, it will be initialized on the first run.
```console
docker run \
-e ALLOW_EMPTY_PASSWORD=yes \
-v /path/to/mysql-persistence:/bitnami/mysql/data \
bitnami/mysql:latest
```
or by modifying the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/mysql/docker-compose.yml) file present in this repository:
```yaml
services:
mysql:
...
volumes:
- /path/to/mysql-persistence:/bitnami/mysql/data
...
```
> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
## Connecting to other containers
@@ -98,76 +82,14 @@ Using [Docker container networking](https://docs.docker.com/engine/userguide/net
Containers attached to the same network can communicate with each other using the container name as the hostname.
### Using the Command Line
In this example, we will create a MySQL client instance that will connect to the server instance that is running on the same docker network as the client.
#### Step 1: Create a network
```console
docker network create app-tier --driver bridge
```
#### Step 2: Launch the MySQL server instance
Use the `--network app-tier` argument to the `docker run` command to attach the MySQL container to the `app-tier` network.
```console
docker run -d --name mysql-server \
-e ALLOW_EMPTY_PASSWORD=yes \
--network app-tier \
bitnami/mysql:latest
```
#### Step 3: Launch your MySQL client instance
Finally we create a new container instance to launch the MySQL client and connect to the server created in the previous step:
```console
docker run -it --rm \
--network app-tier \
bitnami/mysql:latest mysql -h mysql-server -u root
```
### Using a Docker Compose file
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the MySQL server from your own custom application image which is identified in the following snippet by the service name `myapp`.
```yaml
version: '2'
networks:
app-tier:
driver: bridge
services:
mysql:
image: bitnami/mysql:latest
environment:
- ALLOW_EMPTY_PASSWORD=yes
networks:
- app-tier
myapp:
image: YOUR_APPLICATION_IMAGE
networks:
- app-tier
```
> **IMPORTANT**:
>
> 1. Please update the `YOUR_APPLICATION_IMAGE` placeholder in the above snippet with your application image
> 2. In your application container, use the hostname `mysql` to connect to the MySQL server
Launch the containers using:
```console
docker-compose up -d
```
## Configuration
The following section describes the supported environment variables
### Environment variables
The following tables list the main variables you can set.
#### Customizable environment variables
| Name | Description | Default Value |
@@ -241,7 +163,7 @@ In order to have your custom files inside the docker image you can mount them as
Take into account those scripts are treated differently depending on the extension. While the `.sh` scripts are executed in all the nodes; the `.sql` and `.sql.gz` scripts are only executed in the master nodes. The reason behind this differentiation is that the `.sh` scripts allow adding conditions to determine what is the node running the script, while these conditions can't be set using `.sql` nor `sql.gz` files. This way it is possible to cover different use cases depending on their needs.
> NOTE: If you are importing large databases, it is recommended to import them as `.sql` instead of `.sql.gz`, as the latter one needs to be decompressed on the fly and not allowing for additional optimizations to import large files.
> **NOTE** If you are importing large databases, it is recommended to import them as `.sql` instead of `.sql.gz`, as the latter one needs to be decompressed on the fly and not allowing for additional optimizations to import large files.
### Setting the root password on first run
@@ -252,42 +174,12 @@ The root user and password can easily be setup with the Bitnami MySQL Docker ima
Passing the `MYSQL_ROOT_PASSWORD` environment variable when running the image for the first time will set the password of the `MYSQL_ROOT_USER` user to the value of `MYSQL_ROOT_PASSWORD`.
```console
docker run --name mysql -e MYSQL_ROOT_PASSWORD=password123 bitnami/mysql:latest
```
or by modifying the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/mysql/docker-compose.yml) file present in this repository:
```yaml
services:
mysql:
...
environment:
- MYSQL_ROOT_PASSWORD=password123
...
```
**Warning** The `MYSQL_ROOT_USER` user is always created with remote access. It's suggested that the `MYSQL_ROOT_PASSWORD` env variable is always specified to set a password for the `MYSQL_ROOT_USER` user. In case you want to allow the `MYSQL_ROOT_USER` user to access the database without a password set the environment variable `ALLOW_EMPTY_PASSWORD=yes`. **This is recommended only for development**.
### Allowing empty passwords
By default the MySQL image expects all the available passwords to be set. In order to allow empty passwords, it is necessary to set the `ALLOW_EMPTY_PASSWORD=yes` env variable. This env variable is only recommended for testing or development purposes. We strongly recommend specifying the `MYSQL_ROOT_PASSWORD` for any other scenario.
```console
docker run --name mysql -e ALLOW_EMPTY_PASSWORD=yes bitnami/mysql:latest
```
or by modifying the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/mysql/docker-compose.yml) file present in this repository:
```yaml
services:
mysql:
...
environment:
- ALLOW_EMPTY_PASSWORD=yes
...
```
### Setting character set and collation
It is possible to configure the character set and collation used by default by the database with the following environment variables:
@@ -299,53 +191,10 @@ It is possible to configure the character set and collation used by default by t
By passing the `MYSQL_DATABASE` environment variable when running the image for the first time, a database will be created. This is useful if your application requires that a database already exists, saving you from having to manually create the database using the MySQL client.
```console
docker run --name mysql \
-e ALLOW_EMPTY_PASSWORD=yes \
-e MYSQL_DATABASE=my_database \
bitnami/mysql:latest
```
or by modifying the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/mysql/docker-compose.yml) file present in this repository:
```yaml
services:
mysql:
...
environment:
- ALLOW_EMPTY_PASSWORD=yes
- MYSQL_DATABASE=my_database
...
```
### Creating a database user on first run
You can create a restricted database user that only has permissions for the database created with the [`MYSQL_DATABASE`](#creating-a-database-on-first-run) environment variable. To do this, provide the `MYSQL_USER` environment variable and to set a password for the database user provide the `MYSQL_PASSWORD` variable. MySQL supports different authentication mechanisms, such as `caching_sha2_password` or `mysql_native_password`. To set it, use the `MYSQL_AUTHENTICATION_PLUGIN` variable.
```console
docker run --name mysql \
-e ALLOW_EMPTY_PASSWORD=yes \
-e MYSQL_USER=my_user \
-e MYSQL_PASSWORD=my_password \
-e MYSQL_DATABASE=my_database \
-e MYSQL_AUTHENTICATION_PLUGIN=mysql_native_password \
bitnami/mysql:latest
```
or by modifying the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/mysql/docker-compose.yml) file present in this repository:
```yaml
services:
mysql:
...
environment:
- ALLOW_EMPTY_PASSWORD=yes
- MYSQL_USER=my_user
- MYSQL_PASSWORD=my_password
- MYSQL_DATABASE=my_database
...
```
**Note!** The `root` user will be created with remote access and without a password if `ALLOW_EMPTY_PASSWORD` is enabled. Please provide the `MYSQL_ROOT_PASSWORD` env variable instead if you want to set a password for the `root` user.
### Setting up a replication cluster
@@ -363,139 +212,16 @@ A **zero downtime** MySQL master-slave [replication](https://dev.mysql.com/doc/r
In a replication cluster you can have one master and zero or more slaves. When replication is enabled the master node is in read-write mode, while the slaves are in read-only mode. For best performance its advisable to limit the reads to the slaves.
#### Step 1: Create the replication master
The first step is to start the MySQL master.
```console
docker run --name mysql-master \
-e MYSQL_ROOT_PASSWORD=master_root_password \
-e MYSQL_REPLICATION_MODE=master \
-e MYSQL_REPLICATION_USER=my_repl_user \
-e MYSQL_REPLICATION_PASSWORD=my_repl_password \
-e MYSQL_USER=my_user \
-e MYSQL_PASSWORD=my_password \
-e MYSQL_DATABASE=my_database \
bitnami/mysql:latest
```
In the above command the container is configured as the `master` using the `MYSQL_REPLICATION_MODE` parameter. A replication user is specified using the `MYSQL_REPLICATION_USER` and `MYSQL_REPLICATION_PASSWORD` parameters.
#### Step 2: Create the replication slave
Next we start a MySQL slave container.
```console
docker run --name mysql-slave --link mysql-master:master \
-e MYSQL_REPLICATION_MODE=slave \
-e MYSQL_REPLICATION_USER=my_repl_user \
-e MYSQL_REPLICATION_PASSWORD=my_repl_password \
-e MYSQL_MASTER_HOST=mysql-master \
-e MYSQL_MASTER_ROOT_PASSWORD=master_root_password \
bitnami/mysql:latest
```
In the above command the container is configured as a `slave` using the `MYSQL_REPLICATION_MODE` parameter. The `MYSQL_MASTER_HOST`, `MYSQL_MASTER_ROOT_USER` and `MYSQL_MASTER_ROOT_PASSWORD` parameters are used by the slave to connect to the master. It also takes a dump of the existing data in the master server. The replication user credentials are specified using the `MYSQL_REPLICATION_USER` and `MYSQL_REPLICATION_PASSWORD` parameters and should be the same as the one specified on the master.
You now have a two node MySQL master/slave replication cluster up and running. You can scale the cluster by adding/removing slaves without incurring any downtime.
With Docker Compose the master/slave replication can be setup using:
```yaml
version: '2'
services:
mysql-master:
image: bitnami/mysql:latest
ports:
- 3306
volumes:
- /path/to/mysql-persistence:/bitnami/mysql/data
environment:
- MYSQL_REPLICATION_MODE=master
- MYSQL_REPLICATION_USER=repl_user
- MYSQL_REPLICATION_PASSWORD=repl_password
- MYSQL_ROOT_PASSWORD=master_root_password
- MYSQL_USER=my_user
- MYSQL_PASSWORD=my_password
- MYSQL_DATABASE=my_database
mysql-slave:
image: bitnami/mysql:latest
ports:
- 3306
depends_on:
- mysql-master
environment:
- MYSQL_REPLICATION_MODE=slave
- MYSQL_REPLICATION_USER=repl_user
- MYSQL_REPLICATION_PASSWORD=repl_password
- MYSQL_MASTER_HOST=mysql-master
- MYSQL_MASTER_PORT_NUMBER=3306
- MYSQL_MASTER_ROOT_PASSWORD=master_root_password
```
Scale the number of slaves using:
```console
docker-compose up --detach --scale mysql-master=1 --scale mysql-slave=3
```
The above command scales up the number of slaves to `3`. You can scale down in the same manner.
> **Note**: You should not scale up/down the number of master nodes. Always have only one master node running.
If your master database is missing some binary files, the replication will break. It's possible to add `MYSQL_REPLICATION_SLAVE_DUMP=true` to make a dump on the master and import it on the slave.
> **Note**: The master database must be only used by this process until the end to avoid missing data.
### Configuration file
The image looks for user-defined configurations in `/opt/bitnami/mysql/conf/my_custom.cnf`. Create a file named `my_custom.cnf` and mount it at `/opt/bitnami/mysql/conf/my_custom.cnf`.
For example, in order to override the `max_allowed_packet` directive:
#### Step 1: Write your `my_custom.cnf` file with the following content
```config
[mysqld]
max_allowed_packet=32M
```
#### Step 2: Run the MySQL image with the designed volume attached
```console
docker run --name mysql \
-p 3306:3306 \
-e ALLOW_EMPTY_PASSWORD=yes \
-v /path/to/my_custom.cnf:/opt/bitnami/mysql/conf/my_custom.cnf:ro \
-v /path/to/mysql-persistence:/bitnami/mysql/data \
bitnami/mysql:latest
```
or by modifying the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/mysql/docker-compose.yml) file present in this repository:
```yaml
services:
mysql:
...
volumes:
- /path/to/mysql-persistence:/bitnami/mysql/data
- /path/to/my_custom.cnf:/opt/bitnami/mysql/conf/my_custom.cnf:ro
...
```
After that, your changes will be taken into account in the server's behaviour.
Refer to the [MySQL server option and variable reference guide](https://dev.mysql.com/doc/refman/8.0/en/server-options.html) for the complete list of configuration options.
#### Overwrite the main Configuration file
It is also possible to use your custom `my.cnf` and overwrite the main configuration file.
```console
docker run --name mysql -v /path/to/my.cnf:/opt/bitnami/mysql/conf/my.cnf:ro bitnami/mysql:latest
```
### FIPS configuration in Bitnami Secure Images
The Bitnami MySQL Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
@@ -519,56 +245,6 @@ FROM bitnami/mysql
### Put your customizations below
...
```
Here is an example of extending the image with the following modifications:
- Install the `vim` editor
- Modify the MySQL configuration file
- Modify the ports used by MySQL
- Change the user that runs the container
```Dockerfile
FROM bitnami/mysql
### Change user to perform privileged actions
USER 0
### Install 'vim'
RUN install_packages vim
### Revert to the original non-root user
USER 1001
### modify configuration file.
RUN ini-file set --section "mysqld" --key "collation-server" --value "utf8_general_ci" "/opt/bitnami/mysql/conf/my.cnf"
### Modify the ports used by MySQL by default
## It is also possible to change these environment variables at runtime
ENV MYSQL_PORT_NUMBER=3307
EXPOSE 3307
### Modify the default container user
USER 1002
```
Based on the extended image, you can use a Docker Compose file like the one below to add other features:
- Add a custom configuration
```yaml
version: '2'
services:
mysql:
build: .
ports:
- 3306:3307
volumes:
- /path/to/my_custom.cnf:/opt/bitnami/mysql/conf/my_custom.cnf:ro
- data:/bitnami/mysql/data
volumes:
data:
driver: local
```
## Logging
The Bitnami MySQL Docker image sends the container logs to the `stdout`. To view the logs:
@@ -583,7 +259,7 @@ or using Docker Compose:
docker-compose logs mysql
```
To increase the verbosity on intialization or add extra debug information, you can assign the `BITNAMI_DEBUG` environment variable to `true`.
To increase the verbosity on initialization or add extra debug information, you can assign the `BITNAMI_DEBUG` environment variable to `true`.
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
@@ -594,94 +270,12 @@ By default MySQL doesn't enable [slow query log](https://dev.mysql.com/doc/refma
- `MYSQL_ENABLE_SLOW_QUERY`: Whether to enable slow query logs. Default: `0`
- `MYSQL_LONG_QUERY_TIME`: How much time, in seconds, defines a slow query. Default: `10.0`
Slow queries information is logged to the `<data-dir>/<hostname>-slow.log` file by default, and you can easily check it with the `mysqldumpslow` tool ([link to docs](https://dev.mysql.com/doc/refman/en/mysqldumpslow.html)):
```console
$ docker run -d -e MYSQL_ENABLE_SLOW_QUERY=1 -e ALLOW_EMPTY_PASSWORD=yes --name my-mysql-container bitnami/mysql
# wait a bit for the initialization process...
$ docker exec -it my-mysql-container mysqldumpslow
Reading mysql slow query log from /bitnami/mysql/data/<hostname>-slow.log
Count: 1 Time=0.01s (0s) Lock=0.00s (0s) Rows=0.0 (0), root[root]@localhost
GRANT ALL PRIVILEGES ON *.* TO 'S'@'S' WITH GRANT OPTION
Count: 1 Time=0.01s (0s) Lock=0.00s (0s) Rows=0.0 (0), root[root]@localhost
CREATE USER 'S'@'S'
Count: 1 Time=0.01s (0s) Lock=0.00s (0s) Rows=0.0 (0), root[root]@localhost
DELETE FROM mysql.user WHERE user not in ('S','S')
Count: 1 Time=0.00s (0s) Lock=0.00s (0s) Rows=0.0 (0), root[root]@localhost
flush privileges
(...)
```
Slow queries information is logged to the `<data-dir>/<hostname>-slow.log` file by default, and you can easily check it with the `mysqldumpslow` tool ([link to docs](https://dev.mysql.com/doc/refman/en/mysqldumpslow.html)).
### Slow filesystems
In some platforms, the filesystem used for persistence could be slow. That could cause the database to take extra time to be ready. If that's the case, you can configure the `MYSQL_INIT_SLEEP_TIME` environment variable to make the initialization script to wait extra time (in seconds) before proceeding with the configuration operations.
## Maintenance
### Upgrade this image
Bitnami provides up-to-date versions of MySQL, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
#### Step 1: Get the updated image
```console
docker pull bitnami/mysql:latest
```
or if you're using Docker Compose, update the value of the image property to
`bitnami/mysql:latest`.
#### Step 2: Stop and backup the currently running container
Stop the currently running container using the command
```console
docker stop mysql
```
or using Docker Compose:
```console
docker-compose stop mysql
```
Next, take a snapshot of the persistent volume `/path/to/mysql-persistence` using:
```console
rsync -a /path/to/mysql-persistence /path/to/mysql-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)
```
#### Step 3: Remove the currently running container
```console
docker rm -v mysql
```
or using Docker Compose:
```console
docker-compose rm -v mysql
```
#### Step 4: Run the new image
Re-create your container from the new image.
```console
docker run --name mysql bitnami/mysql:latest
```
or using Docker Compose:
```console
docker-compose up mysql
```
> **Note**: Automatic upgrade behavior at startup can be changed setting the env var `MYSQL_UPGRADE`. More information [here](https://dev.mysql.com/doc/refman/8.0/en/server-options.html#option_mysqld_upgrade)
## Notable Changes
### 8.0.37-debian-12-r6, 8.3.0-debian-12-r15, 8.4.0-debian-12-r7
@@ -730,12 +324,6 @@ $ docker-compose up -d
- `ALLOW_EMPTY_PASSWORD` has been added to the available env variables. It can be used to allow blank passwords for MySQL.
- By default the MySQL image requires a root password to start. You can specify it using the `MYSQL_ROOT_PASSWORD` env variable or disable this requirement by setting the `ALLOW_EMPTY_PASSWORD` env variable to `yes` (testing or development scenarios).
## Using `docker-compose.yaml`
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/mysql).
If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md).
## License
Copyright &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.