I'm finding that i cant' keep my WSL image time synced... ntp and chronyd both fail
bash-4.2# sudo service chronyd start
Redirecting to /bin/systemctl start chronyd.service
Failed to get D-Bus connection: Operation not permitted
The temp fix, was to update it manually.
bash-4.2# sudo ntpdate pool.ntp.org
5 Sep 10:49:17 ntpdate[5592]: step time server 43.252.70.34 offset 3455.750697 sec
This was affecting my ability to connect to AWS with temporary credentials as the time was sufficently wrong that it would not stay in sync.
It appears that if i shut down my machine, the wsl machine clock actually stops, were as the host machine's clock does'nt, and it restarts from where it started off.
I'm finding that i cant' keep my WSL image time synced... ntp and chronyd both fail
bash-4.2# sudo service chronyd start
Redirecting to /bin/systemctl start chronyd.service
Failed to get D-Bus connection: Operation not permitted
The temp fix, was to update it manually.
bash-4.2# sudo ntpdate pool.ntp.org
5 Sep 10:49:17 ntpdate[5592]: step time server 43.252.70.34 offset 3455.750697 sec
This was affecting my ability to connect to AWS with temporary credentials as the time was sufficently wrong that it would not stay in sync.
It appears that if i shut down my machine, the wsl machine clock actually stops, were as the host machine's clock does'nt, and it restarts from where it started off.