[Bug]: win11 won't boot about windows

[OlivierArgentieri]

I think i got the same issue.

Environment:

• Ryzen 9 3950X
• 128G RAM
• Windows 10 22h2 19045.3930
• WSL2

I'm trying to run it without kvm

Docker compose

version: "3"
services:
  windows:
    image: dockurr/windows
    container_name: windows
    environment:
      VERSION: "win11"
      KVM: "N"
      CONSOLE: "Y"
      CPU_CORES:  "8" # I also tried to remove quotes char
      DISK_SIZE: "100G"
      RAM_SIZE: "8G"
      HV: "N" # I tried to remove it also
      BOOT_MODE: "windows_plain" # i also try with UEFI
    cap_add:
      - NET_ADMIN
    ports:
      - 8006:8006
      - 3389:3389/tcp
      - 3389:3389/udp
    stop_grace_period: 2m
    restart: on-failure

Result

Tell me if it's not related to this issue.

Edit: ( I also tried on an intel macbook pro (A1707 16G of ram), with this same docker compose and i got the exact same result)

[kroese]

@OlivierArgentieri That message is normal behaviour. It means because the harddrive is empty, it will boot from cd-rom. After Windows is installed and the harddrive is no longer empty, you will not see that message again.

So your only problem seems to be that it keeps hanging on the spinning circle instead of starting the installation.

But even if we do the effort of finding the reason, Im not sure if its worth it, because without KVM the machine will be pretty slow and not really useable for anything serious.

To use KVM you need to upgrade to Windows 11, because Docker Desktop for Windows 10 does not support it. It seems other people who are running Win10 have the exact same problem as you, see: #359 for example.

[dingetje]

I've increased my WSL RAM in .wslconfig to 8GB but didn't notice a change in the reported RAM size, so in addition added an explicit RAM size and now the win11 ran to completion:

[kroese]

In the screenshot it says that you have 3GB of RAM available in your WSL2 instance. And the default RAM_SIZE this container sets is 4GB.

So probably it exits because it cannot allocate the 4GB of RAM. So either change your WSL config to allow more than 3GB or otherwise change your run command to use less (-e "RAM_SIZE=2GB"). If this fixes your issue, I will add an automatic check in the next release that verifies that the amount of RAM available is never lower than the value of RAM_SIZE.

[thetredev]

You could also increase your WSL system's RAM in your .wslconfig file in your Windows home directory, assuming your machine has enough RAM to begin with.

[matifali]

I think I also have the same issue I am stuck at

docker run -it --rm --name windows -p 8006:8006 --device=/dev/kvm --cap-add NET_ADMIN --stop-timeout 120 dockurr/windows
❯ Starting Windows for Docker v3.01...
❯ For support visit https://github.com/dockur/windows
BdsDxe: loading Boot0004 "Windows Boot Manager" from HD(1,GPT,FD4B275D-953A-4181-95F0-26E5FFBCD081,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: starting Boot0004 "Windows Boot Manager" from HD(1,GPT,FD4B275D-953A-4181-95F0-26E5FFBCD081,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi

[kroese]

@OlivierArgentieri If you set RAM_SIZE to 2G, does it make a difference?

[OlivierArgentieri]

@OlivierArgentieri If you set RAM_SIZE to 2G, does it make a difference?

Thank you for your reply !

No i got the same result.

[matifali]

@OlivierArgentieri This means its running connect to that port and you will see that Widows is installing

[OlivierArgentieri]

@OlivierArgentieri This means its running connect to that port and you will see that Widows is installing

But i mean, it's loading endlessly like this:

Are this message the error message or it's just the normal behavior ?
BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found