-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timezone setting on MacOS broken again #61
Comments
It does appear that passing the time zone via TZ as an environment variable is more stable than trying to link the time zone file directly. The main question is how to reliably get the time zone string from the host OS. On reasonably recent Debian, Ubuntu, and MacOS at least, the Ubuntu and Debian both seem to support reading
|
We could also delete the symlink in the container, of course. Not sure if that throws anything into disarray. |
Just use TZ. It's meant to be there (POSIX standard). /etc/localtime is a GNU extension that makes things faster if it's there. |
TZ is unfortunately not set on most platforms I tried (in fact, it was set only on Debian). It works when I set it in the container, but my main problem is trying to get the correct time zone string from the host. |
Yes, adding MacOS support was a real spanner in the works, unfortunately :( What does the Otherwise, your bullet point list of options sounds fair enough. |
For the timezone file itself I get the following on MacOS:
Before I try all that extraction stuff, I'll give it the old method another shot by deleting the symbolic link in the docker container so that there is no conflict when docker is trying to mount there. Peter mentioned that if the file/link does not exist it's just going to default to UTC which is what it's already doing anyway, so there should be no additional adverse effects if the mount command doesn't work for some reason. |
Hi all, also run into the wall of getting the docker image up and running on an M1 Mac, I've set the environment var When running
|
This actually seems to have worked fine, so I’m closing this issue for now. |
It looks like a new form of #16 has reappeared. For
I'm getting
If I delete the time zone line and inspect the container, there is indeed already a symlink in
/etc/localtime
:This is on MacOS Ventura (13.0.1) and Docker version 20.10.21, build
baeda1f
The text was updated successfully, but these errors were encountered: