Where do Docker containers get their time information? I've created some containers from the basic ubuntu:trusty image, and when I run it and request 'date', I get UTC time.

For awhile I got around this by doing the following in my Dockerfile:

RUN sudo echo "America/Los_Angeles" > /etc/timezone

However, for some reason that stopped working. Searching online I saw the below suggested:

docker run -v /etc/timezone:/etc/timezone [image-name]

Both these methods correctly set the timezone though!

$ cat /etc/timezone
America/Los_Angeles
$ date
Tue Apr 14 23:46:51 UTC 2015

Anyone know what gives?

migrated from stackoverflow.com Apr 17 '15 at 17:15

This question came from our site for professional and enthusiast programmers.

up vote 116 down vote accepted

The secret here is that dpkg-reconfigure tzdata simply creates /etc/localtime as a copy, hardlink or symlink (a symlink is preferred) to a file in /usr/share/zoneinfo. So it is possible to do this entirely from your Dockerfile. Consider:

ENV TZ=America/Los_Angeles
RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone

And as a bonus, TZ will be set correctly in the container as well.

This is also distribution-agnostic, so it works with pretty much anything Linux.

Note: If you are using an alpine based image you have to install the tzdata first. (see this issue here)

Looks line this:

RUN apk add --no-cache tzdata
ENV TZ America/Los_Angeles

Usually it is sufficient to set an environment variable in the docker container, like so:

docker run -e TZ=Europe/Amsterdam debian:jessie date

Of course this would work also with docker-compose.

  • 2
    This seems to be the most elegant way. Take care that some base image, like ubuntu:16.04, does not have the tzdata package which should be added in Dockerfile. – Julien Fastré May 19 '17 at 10:25
  • +1 -- I agree with Julien; this appears to be the most elegant approach for setting time zones at runtime. This works well with CentOS. Alpine image does require installation of 'tzdata' package, which is preferred over harcoding configurations at build time unless the extra 3MB image payload cannot be tolerated :) – Frelling Dec 27 '17 at 16:09

Mounting /etc/localtime in the image, so it is in sync with host -v is the most popular one.

But see issue 12084:

it is not correct because it does not work when the software requires instead the file /etc/timezone to be set.
That way you are using leaves it as the default value etc/UTC.

I have determined that actually there is no foolproof elegant way to set the time zone inside of a docker container.
So have finally settled on this solution:

App dockerfile:

# Relocate the timezone file
RUN mkdir -p /config/etc && mv /etc/timezone /config/etc/ && ln -s /config/etc/timezone /etc/

App entrypoint script:

# Set timezone as specified in /config/etc/timezone
dpkg-reconfigure -f noninteractive tzdata

Data volume /config dockerfile, localized to a specific country or region:

# Set the time zone
RUN echo "Europe/London" > /config/etc/timezone

... it is not elegant because involving 3 separate files, and re-creating /etc/localtime on every runtime container start. Which is rather wasteful.

However it does work properly, and successfully achieve separation between the base app image, and each per-country localized configuration.
In 3 lines of code.

You can add your local files (/etc/timezone and /etc/localtime) as volume in your docker-container.

Update your docker-compose.yml with the following lines.

volumes:
    - "/etc/timezone:/etc/timezone:ro"
    - "/etc/localtime:/etc/localtime:ro"

Now the container time is the same as on your host

  • If your on CentOS distrib host enter the command echo "Europe/Paris" > /etc/timezone before restarting the container. – CrazyMax Sep 18 '17 at 13:21
  • Does this work on MacOS host? – Redsandro Oct 26 '17 at 23:24
  • Does not WORK in MAC – Marcello de Sales Jan 19 at 3:08
  • This used to work on MacOS but I just tried it again after a long time and I get the following. Not sure if High Sierra or a docker change caused this: "docker: Error response from daemon: Mounts denied: The path /etc/localtime is not shared from OS X and is not known to Docker. You can configure shared paths from Docker -> Preferences... -> File Sharing. See docs.docker.com/docker-for-mac/osxfs/#namespaces for more info." – gae123 Mar 4 at 2:22
  • This will corrupt your zoneinfo db as /etc/localtime is a symlink (thus /usr/share/zoneinfo/Some/Thing is likely to get mounted as /usr/share/zoneinfo/UTC inside the container). Not to mention that you'd mix the db file from the host with the one in the container. – ionelmc May 10 at 15:03

In ubuntu 16.04 image there is bug. Solution was

    ENV TZ 'Europe/Tallinn'
    RUN echo $TZ > /etc/timezone && \
    apt-get update && apt-get install -y tzdata && \
    rm /etc/localtime && \
    ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && \
    dpkg-reconfigure -f noninteractive tzdata && \
    apt-get clean
  • Seriously...this is the only solution that worked! – Gerrat Jun 30 '17 at 22:13
  • Also had to do this - seems tzdata is no longer in some distros by default. – Peter Jan 24 at 7:06

if you are using docker image based on ubuntu :

# Change the docker default timezone from UTC to SGT
echo "Asia/Singapore" > /etc/timezone
dpkg-reconfigure tzdata
date

Thanks to VonC for the information and link to the issue. This seems like such a convoluted mess, so I did some testing on my own idea of how to solve this and it seems to work great.

>docker run -it ubuntu:trusty /bin/bash
#dpkg-reconfigure tzdata

(follow prompts to select my timezone)

>docker commit [container-id] chocko/ubuntu:local

Then I updated my Dockerfiles to reflect this:

FROM chocko/ubuntu:local

There must be something wrong with this because it seems too easy to be overlooked... Or is this acceptable?

  • This is also what I tried, but the timezone still resets itself after I exit the container. This is on Debian. – Mike Chamberlain Jun 9 '17 at 4:57
  • @MikeChamberlain did you happen to try the accepted answer by Michael Hampton above? I haven't implemented it myself, but I reckon it's the way to go considering the upvotes that it has received. – Chockomonkey Jun 9 '17 at 17:00

Adding my two cents here, because I've tried several of these but none worked on alpine-based images.

However, this did the trick:

ENV TZ=America/Toronto
RUN apk update
RUN apk upgrade
RUN apk add ca-certificates && update-ca-certificates
RUN apk add --update tzdata
RUN rm -rf /var/cache/apk/*

[Source]

A more generic way to set the timezone in docker run arguments:

-e TZ=`ls -la /etc/localtime | cut -d/ -f8-9`

Or for reuse:

function GET_TZ () {
    ls -la /etc/localtime | cut -d/ -f8-9
}

...
-e TZ=`GET_TZ`

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.