The most common things that would trigger this are critically low battery or overheating. It might be good to use something like gkrellm to monitor your temperature internals. I’ve also had cases where I’ve plugged my laptop into a socket that was only active when a light switch was on, so it was draining over night when the light was turned off.
When the machine reboots unintentionally the next time, check sudo journalctl --boot=-1 , which will show you all logs of the last boot (thus, logs of the boot that ended up with an unintentionally reboot). Go to the end of the logs (the last minute before the “–boot=-1” logs end) and check out what happened. If you are not sure how to interpret that, feel free to show us these logs. The last two minutes of the “–boot=-1”-logs should be sufficient to be sure that everything related is contained.
These are definitely realistic possibilities. However, I suggest checking the logs first before taking any action. Temperature and battery issues are contained in the logs.
I have been waiting For the System to reboot for sometime.
I can’t make out what the error on the LOG is but it has something to do with DOCKER or the GNOME SHELL Crashing because that’s the only error i have when a ran the command you have given, and checked the timestamp with the exact reboot
Will make more test. After the couple of updates from Fedora it does not reboot
i will post some of my log here after it reboots again.
Without further information (such as the logs of the journal), I am also not able to tell you much about the issue. An issue like this can have multiple origins. Detailed information of what is happening on the system is necessary.