Error message when trying to switch to windows container

Docker Desktop for Windows
#7

Same error just starting Docker Desktop V3.5.2. Tried removing all of Docker and installing 3.6. It worked until restart of PC then same error again.

Crash report ID: 49FEEE43-F0CA-4093-A027-352232114658/20210817063436

1 Like
#8

During some investigation,

I found few articles mentioned the vEthernet (nat) may not be started automatically after Windows reboot, this phenomenon is similar from my case, the ā€œturn-on of Windows Containerā€ will create the ā€œvEthernet (nat)ā€ and the Windows container does well even I restart Docker several times:
image

And then, those virtual ethernet card are gone after reboot:
image

I donā€™t know if this is correct direction, I even compared the Windows Registry, the major difference after turning on the Windows container is some ethernet settings.

Reference

Set up a NAT network | Microsoft Docs
如何äæ®å¾© Docker Desktop for Windows 各ēخ儇ę€Ŗēš„ē¶²č·Æ問锌 | The Will Will Web

1 Like
#9

Iā€™m having the same issue where Iā€™m not able to switch to windows containers.

  1. Re-installing Docker for Windows desktop (did not resolve the issue)
  2. Disabling Hyper-V and re-enabling it (including restart after disable and a restart after re-enable). Also did not resolve the issue.

Iā€™ve uploaded a crash report, hereā€™s the diag ID; 7DBE08D5-60BA-4D90-B924-9B84C2AF76CF/20210817111122

Hoping for a quick solution :slight_smile:

1 Like
#10

There is a solution available in this github issue; Crash while switching from Linux to Windows containers Ā· Issue #11899 Ā· docker/for-win Ā· GitHub

In short;

  1. Go to C:\ProgramData\Docker
  2. Right click on panic.txt ā†’ Properties
  3. Uncheck ā€˜Read-Onlyā€™
20 Likes
#11

Thank you very much for this solution. Yes, it worked for me. I unchecked the ā€˜Read-Onlyā€™ on the panic.txt file and then did the switch to windows containers, and it switched successfully.

#12

Thanks @tomasslaman , you really saved my day. And finally, I can go sleep well XD

#13

@tomasslaman thank you for the tip when there was no other possible solution.
I had panic.log in my local instead of panic.txt

#14

Thank you @tomasslaman, this has been frustrating me for days.

Out of interest, how did you come across this fix? I have been trawling the net and this thread is the first i have found mentioning it.

#15

I stumbled upon a post after carefully going through all git issues that seemed similar, it was buried a bit more down already with not a lot of traction on the thread. So little bit of luck :wink:

2 Likes
#17

Thank you so much, it was driving me crazy, hope the docker team finds a permenant fix for this.
sorry I ment tomasslaman

#18

Just to say thanks after hours of pulling my hair out I found your postā€¦what a random fix!

#19

Thank you very much. This resolved my issue as well!

#20

Many thank the the suggestion, it works now.

#21

Same again, thankyou.

#22

Thanks. It works now.

#23

Fixed it for me, nice one

#24

I think the problem appears when we update Docker with a non-admin user.
After changing the permissions on the panic file, I had to restart Docker with Admin permissions and it configured everything fine.

#25

Thanks @tomasslaman This saved my day

#26

In version 4.3.2, My problem is resolved with your solution

very thanks

#27

When I saw your reply I though that you are joking or somethingā€¦ Thanks a lot saved my day