Bobcares

Installing MySQL in Docker Container – Here’s how we do it

by | Sep 23, 2020

Installing MySQL in docker container is an easy process which can be done by pulling a docker image, deploying the MySQL container and connecting to the MySQL Docker Container

Here at Bobcares, we have seen several such Docker related queries as part of our Docker Hosting Support for Docker users, web hosts, and online service providers.

Today we’ll take a look at how to install MySQL in Docker.

 

Installing MySQL in Docker Container

Here are the steps our Support Engineers follow to install MySQL.

1. The first step is to pull the docker image. Here we are downloading the latest release. However, if you wish to install a particular version then you can replace the latest tag with the version number.

docker pull mysql/mysql-server:latest

2. Then verify if your image is locally stored or not by running the below command.

docker images

3. Once we have the docker image, now we deploy the container by running the command:

docker run --name=[container_name] -d mysql/mysql-server:latest

4. Now, check if MySQL container is running or not by running the below command.

docker ps

5. Connect to the MySQL docker container.

  • Make sure to install the MySQL client package before connecting to MySQL server.
    apt-get install mysql-client
  • Within the container, start the MySQL client by running the command.
    docker exec -it [container_name] mysql -uroot -p
  • Provide root password when asked for. Then you can change the root password by replacing [newpassword] with a strong password below.
    mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY '[newpassword]';

 

Configuring MySQL Container

The configuration options of the MySQL container are present in the directory /etc/mysql/my.cnf

In order to modify the configuration, we can create an alternative config file on the host machine and mount them inside the container.

1. Initially, we create a new directory on the host machine:

mkdir -p /root/docker/[container_name]/conf.d

2. Then we create a custom MySQL config file inside that directory:

nano /root/docker/[container_name]/conf.d/my-custom.cnf

3. Now we add the lines with the desired configuration.

4. After adding, we save and exit the file.

5. We remove and rerun the MySQL container so that the changes reflect.

Here is the command to run the container and map the volume path

docker run \
--detach \
--name=[container_name]\
--env="MYSQL_ROOT_PASSWORD=[my_password]" \
--publish 6603:3306 \
--volume=/root/docker/[container_name]/conf.d:/etc/mysql/conf.d \
mysql

6. Finally, we run the below command to check whether the container loaded the configuration from the host.

mysql -uroot -pmypassword -h127.0.0.1 -P6603 -e 'show global variables like "max_connections"';

[Need any further assistance with Docker related queries? – We’re available 24*7]

 

Conclusion

In today’s writeup, we saw how our Support Engineers installed and configured the MySQL in Docker container.

Are you using Docker based apps?

There are proven ways to get even more out of your Docker containers! Let us help you.

Spend your time in growing business and we will take care of Docker Infrastructure for you.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF