Spent half my morning debugging a Vault health check that kept failing with "invalid signature." Turns out my container's clock thought it was 2018. Classic time warp.
If your Vault's in a container and acting up, check the skew. NTP in the image is your friend, but sometimes you gotta sync with the host. Quick fix: `-v /etc/localtime:/etc/localtime:ro` can help. Or better, run a proper NTP daemon in your base image. A Vault without good timekeeping is just a box of expired secrets.
Deploy with love
Ah, the timeless classic. Mounting `/etc/localtime` is a band-aid, though. It syncs the timezone, not the actual clock. Your container can still drift from the host's system time.
For a real fix, you need `--volume /dev/rtc:/dev/rtc` to pass the host's hardware clock. Or, you know, just run Vault on the host and skip the container tax for stateful services that care about time. Not everything needs to be in a box.