kornelis

Thank you @JorgeB , I hadn't found that page yet. I guess I'll keep my fingers crossed that permanent PCT (Vancouver) will get added soon.

This will also be an issue for servers in British Columbia Canada (TZ Amerca/Vancouver). This year we switched to permanent DST (summer time) I'm running Unraid 7.3.2 . Settings → Date and Time only provides “(UTC-08:00) Pacific Time (US & Canada)”, which sets: timeZone="America/Los_Angeles" /etc/localtime -> /usr/share/zoneinfo/America/Los_Angeles America/Vancouver is not present under /usr/share/zoneinfo. British Columbia has moved to permanent UTC−07:00 in 2026, so America/Vancouver and America/Los_Angeles are no longer equivalent. I verified this using current tzdata inside one of my LinuxServer containers: TZ=America/Vancouver date -d "2026-11-02 12:00:00" → 2026-11-02 12:00:00 MST -0700 TZ=America/Los_Angeles date -d "2026-11-02 12:00:00" → 2026-11-02 12:00:00 PST -0800 There is an additional Docker impact. DockerMan automatically injects the Unraid timezone into containers (Helpers.php adds TZ=$var['timeZone']), so all of my containers were created with TZ=America/Los_Angeles. As a result, after the November 2026 transition, containers inheriting the Unraid timezone will be one hour behind local Vancouver/B.C. time. As a temporary workaround I've explicitly set a container variable to TZ=America/Vancouver on one affected containers whose bundled tzdata contains the Vancouver zone. I'm hoping with the zoneinfo 2026d update in 7.3.3-rc.2 that TZ America/Vancouver will be restored to Unraid's zoneinfo set and the Date & Time GUI provide a Vancouver/B.C. option now that its rules differ from Los Angeles? Can anyone running 7.3.3-rc.2 confirm this?