Docker Community Forums

Share and learn in the Docker community.

Docker/Hyper-V and laptop sleep


(Voltagex) #1

[removed, I got this wrong, although from the reply maybe I was too hasty?]

I had issues listed here about Docker/Hyper-V causing my laptop to wake up when the lid was closed and overheat (!)

http://social.technet.microsoft.com/wiki/contents/articles/7704.client-hyper-v-survival-guide.aspx says this shouldn’t happen and I’ve also modified the power management setting on my wifi card to see if that fixes the problem.

I’m still not sure if Hyper-V is the issue.

You can view my original post by clicking the orange pencil icon. I still think I’m wrong.


(Thomas Chacko) #2

Yes. This was a nuisance when Windows 10 went public mid-2015 and esp some models of HP and Dell laptops had this issue. Most disabled Hyper-V back then and also rollbacked Intel MEI driver. Now enabling Hyper-V again resurrects this issues -when fast-boot is enabled and Hyper-V does not allow suspending windows sometimes and system does not shutdown/sleep/hibernate (intermiddent issue)

Hyper-V also causes issues with Oracle VirtualBox and Vmware Worstation/ Player - hence both cannot anyway co-exist same time for developers who like to keep Docker Toolbox as well as review Docker for Windows Beta. Also Hyper-V requirement for a Windows 10 Pro license is an expensive one which majority of non-corporate developers does not have or afford or justify.

I believe the Alpine Linux/ xhyve on OS X is a good choice - fast, Yosemite+ native, light weight and no issues with Virtualbox/Vmware fusion co-existing too. Hyper-V though a supposedly ‘native’ virtualisation platform on Microsoft is not a well thought off one - but I guess thats a strategic decision Docker had to agree to within the Microsoft partnership. Unless these known issues are ironed out - the microsoft based developer community here will find these compromises a put-off…


(Thomas Chacko) #3

well… I notice this issue with Hyper-V now enabled.


(Voltagex) #4

Sorry @thomasch, I removed the topic because I believe I’m incorrect.

Server Hyper-V removes sleep ability, Client Hyper-V should not.