minikube fails to start a VM from the sleep

[outcoldman]

What Happened?

Every time I try to start a VM, that was created before, it fails with

adjusting system clock: ssh command error:
command : sudo date -s @1732660676
err     : Process exited with status 1
output  : Tue Nov 26 22:37:56 UTC 2024
date: cannot set date: Invalid argument

Attach the log file

minikube start
--extra-config=apiserver.audit-policy-file=/etc/ssl/certs/audit-policy.yaml
--extra-config=apiserver.audit-log-path=-
--insecure-registry=host.minikube.internal:5055
--container-runtime=containerd
--extra-config=kubelet.container-log-max-files=5
--extra-config=kubelet.container-log-max-size=200Mi
😄 minikube v1.34.0 on Darwin 15.1.1 (arm64)
▪ MINIKUBE_HOME=/Volumes/DATA/minikube
✨ Using the parallels driver based on existing profile
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🔄 Restarting existing parallels VM for "minikube" ...
🤦 StartHost failed, but will try again: adjusting system clock: ssh command error:
command : sudo date -s @1732660667
err : Process exited with status 1
output : date: cannot set date: Invalid argument
Tue Nov 26 22:37:47 UTC 2024

🏃 Updating the running parallels "minikube" VM ...
😿 Failed to start parallels VM. Running "minikube delete" may fix it: adjusting system clock: ssh command error:
command : sudo date -s @1732660676
err : Process exited with status 1
output : Tue Nov 26 22:37:56 UTC 2024
date: cannot set date: Invalid argument

❌ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: adjusting system clock: ssh command error:
command : sudo date -s @1732660676
err : Process exited with status 1
output : Tue Nov 26 22:37:56 UTC 2024
date: cannot set date: Invalid argument

╭───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 😿 If the above advice does not help, please let us know: │
│ 👉 https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

Operating System

macOS (Default)

Driver

Parallels

[humb1t]

can confirm same behaviour on mac os for me.