Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: win11 won't boot #449

Closed
1 task done
dingetje opened this issue May 2, 2024 · 10 comments
Closed
1 task done

[Bug]: win11 won't boot #449

dingetje opened this issue May 2, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@dingetje
Copy link

dingetje commented May 2, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Machine specifications

Intel(R) Core(TM) i7-1165G7 @ 2.80GHz, 2803 Mhz, 4 Core(s), 8 Logical Processor(s)/ 32GB RAM

Operating system

Linux LT-ANTOINEM 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Docker version

Docker version 26.0.0, build 2ae903e

Description

Using a Win11, x64 as host, the script fails to boot win11 to completion

Docker compose

docker run -it --rm --name windows -p 8006:8006 --device=/dev/kvm --cap-add NET_ADMIN --stop-timeout 120 -e BOOT_MODE=windows_plain dockurr/windows

Docker log

?

Screenshots (optional)

image

@dingetje dingetje added the bug Something isn't working label May 2, 2024
@kroese
Copy link
Contributor

kroese commented May 2, 2024

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
Copy link

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.

@OlivierArgentieri
Copy link

OlivierArgentieri commented May 2, 2024

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

image

image

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)

@matifali
Copy link

matifali commented May 2, 2024

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/windowsStarting 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
Copy link
Contributor

kroese commented May 2, 2024

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

@OlivierArgentieri
Copy link

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

Thank you for your reply !

No i got the same result.

image

@matifali
Copy link

matifali commented May 2, 2024

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

@OlivierArgentieri
Copy link

@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:
image

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

@kroese
Copy link
Contributor

kroese commented May 3, 2024

@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
Copy link
Author

dingetje commented May 3, 2024

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:

image

image

@kroese kroese closed this as completed May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants