Movatterモバイル変換

Downloading a MySQL Server Docker Image

Downloading the server image in a separate step is not strictly necessary; however, performing this step before you create your Docker container ensures your local image is up to date. To download the MySQL Community Edition image from theOracle Container Registry (OCR), run this command:

docker pull container-registry.oracle.com/mysql/community-server:tag

Thetag is the label for the image version you want to pull (for example,5.7,8.0, orlatest). If:tag is omitted, thelatest label is used, and the image for the latest GA version of MySQL Community Server is downloaded.

To download the MySQL Enterprise Edition image from the OCR, you need to first accept the license agreement on the OCR and log in to the container repository with your Docker client. Follow these steps:

Download the Docker image for MySQL Enterprise Edition from the OCR with this command:

docker pull  container-registry.oracle.com/mysql/enterprise-server:tag

To download the MySQL Enterprise Edition image fromMy Oracle Support website, go onto the website, sign in to your Oracle account, and perform these steps once you are on the landing page:

Unzip the downloaded.zip archive to obtain the tarball inside (mysql-enterprise-server-version.tar), and then load the image by running this command:

docker load -i mysql-enterprise-server-version.tar

You can list downloaded Docker images with this command:

$> docker imagesREPOSITORY                                             TAG       IMAGE ID       CREATED        SIZEcontainer-registry.oracle.com/mysql/community-server   latest    1d9c2219ff69   2 months ago   496MB

Starting a MySQL Server Instance

To start a new Docker container for a MySQL Server, use the following command:

docker run --name=container_name  --restart on-failure -dimage_name:tag

image_name is the name of the image to be used to start the container; seeDownloading a MySQL Server Docker Image for more information.

The--name option, for supplying a custom name for your server container, is optional; if no container name is supplied, a random one is generated.

The--restart option is for configuring therestart policy for your container; it should be set to the valueon-failure, to enable support for server restart within a client session (which happens, for example, when theRESTART statement is executed by a client or during theconfiguration of an InnoDB cluster instance). With the support for restart enabled, issuing a restart within a client session causes the server and the container to stop and then restart.Support for server restart is available for MySQL 8.0.21 and later.

For example, to start a new Docker container for the MySQL Community Server, use this command:

docker run --name=mysql1 --restart on-failure -d container-registry.oracle.com/mysql/community-server:latest

To start a new Docker container for the MySQL Enterprise Server with a Docker image downloaded from the OCR, use this command:

docker run --name=mysql1 --restart on-failure -d container-registry.oracle.com/mysql/enterprise-server:latest

To start a new Docker container for the MySQL Enterprise Server with a Docker image downloaded from My Oracle Support, use this command:

docker run --name=mysql1 --restart on-failure -d mysql/enterprise-server:latest

If the Docker image of the specified name and tag has not been downloaded by an earlierdocker pull ordocker run command, the image is now downloaded. Initialization for the container begins, and the container appears in the list of running containers when you run thedocker ps command. For example:

$> docker psCONTAINER ID   IMAGE                                                         COMMAND                  CREATED          STATUS                    PORTS                       NAMES4cd4129b3211   container-registry.oracle.com/mysql/community-server:latest   "/entrypoint.sh mysq…"   8 seconds ago    Up 7 seconds (health: starting)   3306/tcp, 33060-33061/tcp   mysql1

The container initialization might take some time. When the server is ready for use, theSTATUS of the container in the output of thedocker ps command changes from(health: starting) to(healthy).

The-d option used in thedocker run command above makes the container run in the background. Use this command to monitor the output from the container:

docker logs mysql1

Once initialization is finished, the command's output is going to contain the random password generated for the root user; check the password with, for example, this command:

$> docker logs mysql1 2>&1 | grep GENERATEDGENERATED ROOT PASSWORD: Axegh3kAJyDLaRuBemecis&EShOs

Connecting to MySQL Server from within the Container

Once the server is ready, you can run themysql client within the MySQL Server container you just started, and connect it to the MySQL Server. Use thedocker exec -it command to start amysql client inside the Docker container you have started, like the following:

docker exec -it mysql1 mysql -uroot -p

When asked, enter the generated root password (see the last step inStarting a MySQL Server Instance above on how to find the password). Because theMYSQL_ONETIME_PASSWORD option is true by default, after you have connected amysql client to the server, you must reset the server root password by issuing this statement:

mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'password';

Substitutepassword with the password of your choice. Once the password is reset, the server is ready for use.

Container Shell Access

To have shell access to your MySQL Server container, use thedocker exec -it command to start a bash shell inside the container:

$> docker exec -it mysql1 bashbash-4.2#

You can then run Linux commands inside the container. For example, to view contents in the server's data directory inside the container, use this command:

bash-4.2# ls /var/lib/mysqlauto.cnf    ca.pem     client-key.pem  ib_logfile0  ibdata1  mysql       mysql.sock.lock   private_key.pem  server-cert.pem  sysca-key.pem  client-cert.pem  ib_buffer_pool  ib_logfile1  ibtmp1   mysql.sock  performance_schema  public_key.pem   server-key.pem

Stopping and Deleting a MySQL Container

To stop the MySQL Server container we have created, use this command:

docker stop mysql1

docker stop sends a SIGTERM signal to themysqld process, so that the server is shut down gracefully.

Also notice that when the main process of a container (mysqld in the case of a MySQL Server container) is stopped, the Docker container stops automatically.

To start the MySQL Server container again:

docker start mysql1

To stop and start again the MySQL Server container with a single command:

docker restart mysql1

To delete the MySQL container, stop it first, and then use thedocker rm command:

docker stop mysql1

docker rm mysql1

If you want theDocker volume for the server's data directory to be deleted at the same time, add the-v option to thedocker rm command.

Upgrading a MySQL Server Container

Follow these steps to upgrade a Docker installation of MySQL 5.7 to 8.0:

Follow the same steps for upgrading within the 8.0 series (that is, from release 8.0.x to 8.0.y): stop the original container, and start a new one with a newer image on the old server data and configuration. If you used the8.0 or thelatest tag when starting your original container and there is now a new MySQL 8.0 release you want to upgrade to it, you must first pull the image for the new release with the command:

docker pull container-registry.oracle.com/mysql/community-server:8.0

You can then upgrade by starting anew container with the same tag on the old data and configuration (adjust the image name if you are using the MySQL Enterprise Edition; seeDownloading a MySQL Server Docker Image):

docker run --name=mysql80new \   --mount type=bind,src=/path-on-host-machine/my.cnf,dst=/etc/my.cnf \   --mount type=bind,src=/path-on-host-machine/datadir,dst=/var/lib/mysql \-d container-registry.oracle.com/mysql/community-server:8.0

More Topics on Deploying MySQL Server with Docker

For more topics on deploying MySQL Server with Docker like server configuration, persisting data and configuration, server error log, and container environment variables, seeSection 2.6.2, “More Topics on Deploying MySQL Server with Docker”.