Container timezone causes wrong time attributes from API

Tooa commented 3 years ago

Expected Behavior

When I'm in the Europe/Berlin timezone and I query the API via curl -X GET --header "X-Api-Key: <token>" http://<instance:port>/api/v1/checks/<uuid> then I expect the last_ping attribute to be in the Europe/Berlin timezone

Current Behavior

last_ping attribute from does not return time in my timezone. It is one hour off

Steps to Reproduce

Start docker container
Configure check
Create API token
Query check via curl -X GET --header "X-Api-Key: <token>" http://<instance:port>/api/v1/checks/<uuid>

Discussion and proposed solution

I assume the API uses the timezone set in the container
I propose to add an environment variable TZ=Europe/Berlin that allows to change the timezone of the container

Environment

OS: RaspberryPi OS (buster) CPU architecture: arm32 How docker service was installed: from the official docker repo

Command used to create docker container (run/create/compose/screenshot)

Docker logs

github-actions[bot] commented 3 years ago

Thanks for opening your first issue here! Be sure to follow the issue template!

aptalca commented 3 years ago

Upstream issue: https://gitlab.alpinelinux.org/alpine/aports/-/issues/12057#note_124235

EDIT: It already accepts the TZ var, but it's not working on arm32 due to the linked issue

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

aptalca commented 3 years ago

This was fixed upstream

linuxserver / docker-healthchecks