Solve the problem of inconsistency between mysql time and system time in docker

Recently, when I installed MySQL in Docker, I found that the database time was 8 hours different from the system time.

Linux server time:

Enter mysql and enter date as follows

It turns out that the two time zones are different. Because the MySQL container is installed in Docker, the incorrect MySQL time should be caused by the host Docker.

After searching the data, I found that the default time zone of Docker is zone 0. In fact, this will cause a lot of trouble to the installed container, such as inaccurate execution log records.

There are two solutions:

Method 1: Copy the localtime of the host

docker cp /etc/localtime [container ID or NAME]:/etc/localtime

Note: Due to time zone issues, the above command may report the following error

Error response from daemon: Error processing tar file(exit status 1):

invalid symlink "/usr/share/zoneinfo/UCT" -> "../usr/share/zoneinfo/Asia/Shanghai"

View this file

It was found that this file referenced an address

Solution: Switch Command

docker cp /usr/share/zoneinfo/Asia/Shanghai[container ID or NAME]:/etc/localtime

Then restart the container

docker restart [container ID or NAME]

Method 2: Shared host localtime

Specify startup parameters when creating a container and mount the localtime file into the container

docker run --name -v /etc/localtime container id:/etc/localtime:ro ....

The problem of inconsistent time zones between the two is solved.

This is the end of this article about the inconsistency between mysql time and system time in docker. For more related docker time inconsistency content, please search 123WORDPRESS.COM's previous articles or continue to browse the following related articles. I hope everyone will support 123WORDPRESS.COM in the future!