Docker time is out of sync with host machine
Closed this issue · 1 comments
mrosendin commented
Description
The issue occurs typically when running a polyledger_server Docker container which makes Bitbutter API requests which requires a timestamp in the header. After the host machine goes into hibernation/sleep mode, the time drift occurs.
The end result within the application is a 500 internal server error.
mrosendin commented
This can be resolved by either restarting Docker for Mac or more simply by running the following command in a separate terminal tab:
docker run --rm --privileged polyledger_server hwclock -s
This problem is theorized to only occur on local machines that have sleep mode enabled and therefore should not be an issue on our cloud hosts.