-
Notifications
You must be signed in to change notification settings - Fork 893
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
watchtower ignores mounted /etc/timezone file #876
Comments
Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏 |
I modified the watchtower startup to print some TZ info: Output from running outside docker in a "clean" multipass VM
Output running inside a docker container:
Container was built using Manually loading the correct timezone does work, but according to the docs the file it uses for local time is
Indeed, that works. We should update the docs to reflect this. Some more details regarding this: The only potential problem I can see with binding the hosts |
To avoid important communication to get lost in a closed issues no one monitors, I'll go ahead and lock this issue. If you want to continue the discussion, please open a new issue. Thank you! 🙏🏼 |
Describe the bug
using docker compose, mounted volume for /etc/timezone is ignored
To Reproduce
Expected behavior
Expect to see watchtower operate in mounted timezone in notification timestamps and schedule checking.
Environment
Additional context
watchtower operates in correct timezone if environmental variable TZ is set.
The text was updated successfully, but these errors were encountered: