How to Keep Docker Containers in Sync with Host Timezone

Why Timezone Synchronization Matters

In containerized deployments, matching the container's timezone with the host's is essential for accurate log timestamps, scheduled tasks, and overall application stability. By default Docker runs containers in UTC, which can cause mismatches with host services.

Method 1: Mount Host Timezone Files

Map the host's /etc/localtime and /etc/timezone into the container so it inherits the same settings.

docker run -v /etc/localtime:/etc/localtime:ro -v /etc/timezone:/etc/timezone:ro -d centos:7

Docker Compose example:

version: '3.3'
services:
  your_service:
    image: centos:7
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /etc/timezone:/etc/timezone:ro

Method 2: Use the TZ Environment Variable

Set TZ in a Dockerfile or docker‑compose.yml for more flexibility, especially in multi‑timezone deployments.

FROM ubuntu
ENV TZ=Asia/Shanghai
RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone

Compose version:

version: '3.3'
services:
  your_service:
    image: ubuntu
    environment:
      - TZ=Asia/Shanghai

Using timedatectl on the Host

The timedatectl command lets you view and change the system timezone on Linux (e.g., CentOS). timedatectl | grep "Time zone" Set a new timezone:

sudo timedatectl set-timezone Asia/Shanghai

Dynamic Timezone Setting in Scripts

For automation scripts, you can read a configuration file and export TZ at runtime.

#!/bin/bash
# Assume timezone_config.txt contains a timezone string
TIMEZONE=$(cat timezone_config.txt)
export TZ=$TIMEZONE
echo "Current time: $(date)"

This approach makes scripts configurable and adaptable to different user or regional preferences.

Conclusion

Properly configuring timezone settings for containers and the host ensures consistent behavior, simplifies log management, and helps applications run reliably across global environments.