Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

"ltime" converter does not reflect container timezone

Open
#217 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, shell

Research direction

Start with the Alpine image definitions in the docker-library/haproxy repository and compare them with the Debian variants, which include tzdata. Check the ltime behavior with TZ set in an Alpine container; done means the converter reports the configured container timezone rather than UTC.

Written by the indexing model from the issue text.

Description

ltime reports the server timezone as UTC regardless of what is set as the TZ environment variable in the container.

Adding the tzdata package to the image appears to resolve this issue.

Edit: This happens only in the Alpine variants. The Debian images have always included tzdata in the base image and are thus unaffected.

Dominant language
Shell
Stars
383
Forks
162
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker-library/haproxy

All issues in docker-library/haproxy

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.