uptrace Uptrace not started if clickhouse timezone is different from UTC

When using standard container with uptrace (uptrace/uptrace:2.0.0-beta.1) if connecting clickhouse with any locale different from UTC got error: "unknown time zone XXX/XXX".

It's could be easy fixed by installing tzdata into container

May 12 '25 16:05 dimonb

I've added session_timezone so this does not happen any more.

Thanks for reporting this.

May 13 '25 11:05 vmihailenco

It does not fix anything with container. Set session_timezone parameter, but container doesn't contain any timezones

Jun 16 '25 09:06 dontepanlin

@dontepanlin I assumed that it does not matter with the UTC timezone. And I still think so since it is somehow is working for me...

Jun 16 '25 10:06 vmihailenco

It does not fix anything with container. Set session_timezone parameter, but container doesn't contain any timezones

Can confirm this. To fix the problem created image with added tzdata

Jun 16 '25 15:06 dimonb

It does not fix anything with container. Set session_timezone parameter, but container doesn't contain any timezones

Can confirm this. To fix the problem created image with added tzdata

Yes, i saw your first answer and choose this solution. Btw, image from docker hub does not work out the box.

Jun 17 '25 09:06 dontepanlin

This should be fixed in v2.0.0-rc.1

Jul 07 '25 13:07 vmihailenco