개요Android 개발환경을 설정하며 의도치 않게 WSL2의 구동에 영향을 미치는 환경설정을 변경하였습니다. Show 위 오류 문구를 통해 검색하여, 웹에 제시되어 있는 해결법에 따라 Linux 용 Windows 하위 시스템, 가상 머신 플랫폼 을 비활성화, 재부팅, 활성화, 재부팅하였으나 개선되지 않았습니다. 그래서 검색어를 변경하여 아래와 같이 영문 오류 메시지를 이용하여 검색하여 해결방법을 찾았고 이를 공유합니다. Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.해결문제 확인 및 진단# 관리자 권한으로 cmd 실행 # 진단 C:\Windows\system32>bcdedit Windows 부팅 관리자 -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume2 path \EFI\Microsoft\Boot\bootmgfw.efi description Windows Boot Manager locale ko-KR inherit {globalsettings} default {current} resumeobject {fa42bf7d-49fa-11e9-b4b3-8caa000d495c} displayorder {current} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215} toolsdisplayorder {memdiag} timeout 30 Windows 부팅 로더 ------------------- identifier {current} device partition=C: path \Windows\system32\winload.efi description Windows 10 locale ko-KR inherit {bootloadersettings} recoverysequence {fa42bf7f-49fa-11e9-b4b3-8caa000d495c} displaymessageoverride Recovery recoveryenabled Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {fa42bf7d-49fa-11e9-b4b3-8caa000d495c} nx OptIn bootmenupolicy Standard hypervisorlaunchtype Offhypervisorlaunchtype 항목이 off로 되어 있는 것이 문제라고 합니다. 조치아래와 같이 hypervisorlaunchtype 항목을 auto 로 변경한 후, 재부팅합니다. C:\Windows\system32>bcdedit /set hypervisorlaunchtype auto참고
I like this blog. It took me just 1 article to drop all the attention I was paying for the SEO rules. But let’s move on and try to understand this incompatibility between WSL2 and Docker. ScenarioYou might have been using virtualizations like Hyper-V, VMWare & Co (…no, not you VirtualBox) for a decent number of years now and suddenly Docker comes out and “…PUF…” , it’s such a game changer that you want to keep up with the technology shift. If you like technology there is the chance that you have already installed Windows Subsystem for Linux and if you are an early adopter like myself you have probably left WSL1 for WSL2 because it’s definitely faster and your terminal doesn’t get stuck when using apt-get And here comes the trouble: after the first installation everything looks smoothly and Docker is up and running. Then you go to bed because once again is midnight and they after when you wake up and fire up Docker this is what you get:  You try to reboot the machine, reboot Docker, nothing works. Ironically also your Linux bash doesn’t work. SolutionThe root cause is that Docker uses WSL2 and it has overwritten your previous WSL2 installation. In fact if you run wsl -l -v you will see that both uses WSL2: Is sad but in order to fix this issue I had to
..I know this is not a good news but this is how I fixed it. Downgrading WSL2 to WSL1 won’t help. |
Failed to deploy distro docker desktop Please enable the Virtual Machine Platform Windows feature
zusammenhängende Posts
Urheberrechte © © 2024 IlerngutCOM Inc.
