| 2016-05-01 12:11:25 |
Jeffrey Zhang |
summary |
Normally, the container is using UTC timezone. When the host timezone is changed, the hardware clock will be changed two. But the container know nothing about the change. the the time in the container will offset a few hours, which will result in error in the distribute service. like mariadb galera and ceph.Normally, the container is using UTC timezone. When the host timezone is changed, the hardware clock will be changed two. But the container know nothing about the change. the the time in the container will offset a few hours, which will result in error in the distribute service. like mariadb galera and ceph.Normally, the container is using UTC timezone. When the host timezone is changed, the hardware clock will be changed two. But the container know nothing about the change. the the time in the container will offset a few hours, which will result in error in the distribute service. like mariadb galera and ceph.Normally, the container is using UTC timezone. When the host timezone is changed, the hardware clock will be changed two. But the container know nothing about the change. the the time in the container will offset a few hours, which will result in error in the distribute service. like mariadb galera and ceph.Normally, the container is using UTC timezone. When the host timezone is changed, the hardware clock will be changed two. But the container know nothing about the change. the the time in the container will offset a few hours, which will result in error in the distribute service. like mariadb galera and ceph.Normally, the container is using UTC timezone. When the host timezone is changed, the hardware clock will be changed two. But the container know nothing about the change. the the time in the container will offset a few hours, which will result in error in the distribute service. like mariadb galera and ceph. |
sync the timezone between the host and the containers |
|
