You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... the documentation does not mention anything about my problem
... there are no open or closed issues that are related to my problem
Description
ddns-route53 container seems to ignore TZ variable
Expected behaviour
environment:
- "TZ=Europe/Helsinki"
expecting that Europe/Helsinki time is used by container and shown in logs
Actual behaviour
UTC time is used instead (off by 2 hours)
Tue, 16 Jan 2024 20:46:52 UTC INF Starting ddns-route53 version=v2.11.0
Tue, 16 Jan 2024 20:46:52 UTC INF Configuration loaded from 9 environment variables
Tue, 16 Jan 2024 20:46:52 UTC INF Current WAN IPv4: censored
Tue, 16 Jan 2024 20:46:53 UTC INF WAN IPv4 has not changed for my.little.domain. record set
Tue, 16 Jan 2024 20:46:53 UTC WRN No Route53 record set to update. Skipping...
Tue, 16 Jan 2024 20:46:53 UTC INF Cron initialized with schedule */30 * * * *
Tue, 16 Jan 2024 20:46:53 UTC INF Next run in 13 minutes 6 seconds (2024-01-16 21:00:00 +0000 UTC)
Tue, 16 Jan 2024 20:54:57 UTC INF Starting ddns-route53 version=v2.11.0
Tue, 16 Jan 2024 20:54:57 UTC DBG No configuration file found
Tue, 16 Jan 2024 20:54:57 UTC INF Configuration loaded from 9 environment variables
Tue, 16 Jan 2024 20:54:57 UTC DBG {
"credentials": {
"accessKeyID": "censored",
"secretAccessKey": "censored"
},
"route53": {
"hostedZoneID": "censored",
"recordsSet": [
{
"name": "censored",
"type": "A",
"ttl": 600
},
{
"name": "censored",
"type": "A",
"ttl": 600
}
]
}
}
Tue, 16 Jan 2024 20:54:57 UTC INF Current WAN IPv4: censored
Tue, 16 Jan 2024 20:54:58 UTC INF WAN IPv4 has not changed for censored. record set
Tue, 16 Jan 2024 20:54:58 UTC INF WAN IPv4 has not changed for censored. record set
Tue, 16 Jan 2024 20:54:58 UTC WRN No Route53 record set to update. Skipping...
Tue, 16 Jan 2024 20:54:58 UTC INF Cron initialized with schedule */30 * * * *
Tue, 16 Jan 2024 20:54:58 UTC INF Next run in 5 minutes 1 second (2024-01-16 21:00:00 +0000 UTC)
Additional info
Other containers on the same system (MariaDB, Pi-hole) do not exhibit this issue and respect the TZ value set in docker compose during their operation.
The text was updated successfully, but these errors were encountered:
Support guidelines
I've found a bug and checked that ...
Description
ddns-route53 container seems to ignore TZ variable
Expected behaviour
expecting that Europe/Helsinki time is used by container and shown in logs
Actual behaviour
UTC time is used instead (off by 2 hours)
Tue, 16 Jan 2024 20:46:52 UTC INF Starting ddns-route53 version=v2.11.0
Tue, 16 Jan 2024 20:46:52 UTC INF Configuration loaded from 9 environment variables
Tue, 16 Jan 2024 20:46:52 UTC INF Current WAN IPv4: censored
Tue, 16 Jan 2024 20:46:53 UTC INF WAN IPv4 has not changed for my.little.domain. record set
Tue, 16 Jan 2024 20:46:53 UTC WRN No Route53 record set to update. Skipping...
Tue, 16 Jan 2024 20:46:53 UTC INF Cron initialized with schedule */30 * * * *
Tue, 16 Jan 2024 20:46:53 UTC INF Next run in 13 minutes 6 seconds (2024-01-16 21:00:00 +0000 UTC)
Steps to reproduce
Deploy container as follows:
version: "3.5"
services:
ddns-route53:
image: crazymax/ddns-route53:latest
container_name: ddns-route53
environment:
- "TZ=Europe/Helsinki"
- "SCHEDULE=*/30 * * * *"
- "LOG_LEVEL=info"
- "LOG_JSON=false"
- "DDNSR53_CREDENTIALS_ACCESSKEYID=censored"
- "DDNSR53_CREDENTIALS_SECRETACCESSKEY= censored"
- "DDNSR53_ROUTE53_HOSTEDZONEID= censored"
- "DDNSR53_ROUTE53_RECORDSSET_0_NAME=censored."
- "DDNSR53_ROUTE53_RECORDSSET_0_TYPE=A"
- "DDNSR53_ROUTE53_RECORDSSET_0_TTL=600"
- "DDNSR53_ROUTE53_RECORDSSET_1_NAME= censored."
- "DDNSR53_ROUTE53_RECORDSSET_1_TYPE=A"
- "DDNSR53_ROUTE53_RECORDSSET_1_TTL=600"
restart: always
ddns-route53 version
v2.11.0
Docker info
Docker Compose config
Logs
Additional info
Other containers on the same system (MariaDB, Pi-hole) do not exhibit this issue and respect the TZ value set in docker compose during their operation.
The text was updated successfully, but these errors were encountered: