tunablenormal

I seem to be having a similar issue. I never had krusader set to auto start, so I am use to being able to access the WebUI immediately after starting the Docker. Since I updated to 6.12.6 last week, I've noticed that I cannot access the WebUI for krusader immediately. It is definitely less than an hour in my case though. I think 20min or less. So, it seems to be a slow start issue and not really a show stopper, but it is interesting that it only started after upgrading to 6.12.6.

Thanks for this thread! I'm sure you saved me several hours of searching and digging through 100+ page "support" threads. Just to help those searching in the future, I'm running an ASRock Z370 ITX motherboard and it is also using NCT6775. This tutorial got me up and running in minutes with temps and fan controls. Also, thanks to @ich777 for the link to the details on the risks of enabling acpi_enforce_resources=lax. Its good to have some understanding of what this work around is actually doing.