Timezone desync between host and containers

So our Sentry host is running the latest on-prem version, but it’s not allowing new events. I’ve tracked down the issue as (potentially) being timezone desync, because the time reported by date inside the containers is an hour behind our host. Our host is in UTC+1 (BST) but the containers are in UTC.

Can someone help me out with this?

The containers need to be on UTC to operate correctly as Snuba relies on this (cc @fpacifici). But if that clock is out of sync with the outer world, it may cause events being rejected as they would be deemed “too late”. /cc @untitaker in case I’m making this up.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.