Workaround: starting the 3.2.0-debian docker container on raspbian

[vasu1124 (Vasu)]

And now I am reading that there is a proper workaround documented as well:

Docker openhab:3.2.0-snapshot stuck at unhealthy with OpenJDK Client VM warning: No monotonic clock was available

Raspberry Pi 4, Docker Engine - 20.10.10 openhab:3.2.0-snapshot as the title suggest, I just pulled the latest 3.2.0-snapshot and when I start the openhab I am getting this entry and the container state is either stuck at “starting” or “unhealthy”. not sure if that JDK error is the issue or not. any thoughts? Launching the openHAB runtime... OpenJDK Client VM warning: No monotonic clock was available - timed services may be adversely affected if the time-of-day clock changes please see this …