10 months ago
Hi Railway team,
I'm experiencing timezone errors with "Asia/Calcutta" and "America/Buenos_Aires" that started recently. The errors indicate these are now "Invalid Timezone" despite working fine a week ago.
This appears to be related to the tzdata 2025b update (released March 22, 2025) which may have been applied to your container images or infrastructure.
Could you confirm if:
The tzdata package was updated in your base images recently?
What version of tzdata is currently running in the Railway containers?
If this is indeed the cause, are there any plans to add legacy timezone support or should I implement workarounds at the application level?( I think this should be managed at the application level, so you can ignore this point)
Thanks for your help!
11 Replies
I analysed the build logs from both the versions(one from a weeks ago and one from today) and it seems like
you have updated your Nixpacks base image,
old version was using Ubuntu 22.04 LTS (Jammy Jellyfish)
new version is using ghcr.io/railwayapp/nixpacks:ubuntu-1745885067
It is possible that the new version of base image has the updated tzdata data 🤔
I pulled both the version and checked the tzdata version
`docker pull ghcr.io/railwayapp/nixpacks:ubuntu-1745885067
docker run --rm ghcr.io/railwayapp/nixpacks:ubuntu-1745885067 dpkg -l | grep tzdata
docker pull ghcr.io/railwayapp/nixpacks:debian-1655126806
docker run --rm ghcr.io/railwayapp/nixpacks:debian-1655126806 dpkg -l | grep tzdata`
this confirms my hypothesis
New Image (ubuntu-1745885067):ii tzdata 2025b-0ubuntu0.24.04 all time zone and daylight-saving time data
Using tzdata version 2025b
Based on Ubuntu 24.04
Old Image (debian-1655126806):ii tzdata 2021a-1+deb11u4 all time zone and daylight-saving time data
Using tzdata version 2021a
Based on Debian 11
10 months ago
!t
10 months ago
does the tzdata 2025b update have some known bug or something?
Nothing specifally in 2025b but in previous versions some timezones were moved to ‘tzdata-legacy’ package.
https://askubuntu.com/questions/1532129/difference-in-time-zone-data
(cannot verify this myself as I am on mobile currently)
10 months ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response adam • 10 months ago
10 months ago
this sounds more like an incompatibility in your application
10 months ago
perfect, then there's no action needed on our side
Status changed to Solved ray-chen • 10 months ago