-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Docker: Timezone #7123
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
I think #7792 will fix this that you can set your Location on app.ini |
@noboevbo does my comment resolve your issue ? Can we close it ? |
@sapk sorry for the delay. I just tested it and the timezone issue is fixed! I had to forward the timezone set files like you've suggested. Thanks! |
Perfect. Enjoy using gitea. |
[x]
):Description
There seems to be a problem with the time zone for OpenSSH. In principle I pass the time zone as environment variable via Docker-Compose (- TZ=Europe/Berlin). The gitea logs have the correct timestamp. The SSH logs have a different timestamp, which causes problems when using fail2ban.
Example output:
`
I already tried to set the timezone manually on top of the entrypoint script like this:
ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone && /usr/bin/entrypoint
The date is set correctly (e.h. when executing date), but the sshd log is still showing the wrong time. Does anyone have any idea what else could be wrong with that? Is the timezone possibly not taken over correctly by s6?
The text was updated successfully, but these errors were encountered: