Just noticed today after upgrading to 7.3.0 that some of my containers were not starting. Looks like some zoneinfo file changed?

root@ur:~# ls /etc/localtime 
/etc/localtime@
root@ur:~# ls -l /etc/localtime 
lrwxrwxrwx 1 root root 35 May 14 20:36 /etc/localtime -> /usr/share/zoneinfo/America/Toronto
root@ur:~# ls /usr/share/zoneinfo
Africa/  America/  Asia/  Atlantic/  Australia/  Europe/  Indian/  Pacific/  UTC
root@ur:~# ls /usr/share/zoneinfo/America/
Anchorage  Bogota        Campo_Grande  Cayenne  Chihuahua  Godthab    Halifax   La_Paz       Mexico_City  New_York  Phoenix  Santiago   St_Johns
Asuncion   Buenos_Aires  Caracas       Chicago  Denver     Guatemala  Indiana/  Los_Angeles  Montevideo   Noronha   Regina   Sao_Paulo  Tijuana

I may have missed it, but don't remember seeing that in the release notes.

Is this a bug or new behaviour?

Probably some change in the kernel. What is the time zone set to in Settings - Date and Time?

Mine was set to Europe/Zurich in 7.2 and it's also gone now, setting was reset to GMT-10 and crons ran based on UTC. Had to reset it using the dropdown and it uses Europe/Paris now. Will see if the crons work right again tomorrow...

hi, after the update i setup Europe\Rome timezone, but the link of /etc/localtime was broken (no Rome in Europe)

root@UNRAIDSERVER:/etc# ls /usr/share/zoneinfo/Europe/
Athens  Berlin  Budapest  Istanbul  Kyiv  London  Minsk  Moscow  Paris  Saratov  Warsaw

Now is working, after setting up again the time in DateTime page, and is:

root@UNRAIDSERVER:/etc# ls -l /etc/localtime 
lrwxrwxrwx 1 root root 33 May 18 23:18 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin

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?

The root cause has been found, see my last reply here: https://product.unraid.net/p/7-3-0-removed-zoneinfo-entries-break-existing-timezone-selection

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.