[Bug]: fail to load, not found

[kuyagic]

Operating system

RockyLinux 10

Description

podman log seems ok

but vnc shows not found boot

Docker compose

podman command line

podman run -it --rm \
  --name windows \
  --env VERSION="11" \
  --env DISK_SIZE="100G" \
  --env RAM_SIZE="8G" \
  --env CPU_CORES="4" \
  --env USERNAME="usern" \
  --env PASSWORD="pass" \
  --env USER_PORTS="8006" \
  --env REGION="zh-CN" \
  --network dyweb \
  --device /dev/kvm:/dev/kvm \
  --device /dev/net/tun:/dev/net/tun \
  --cap-add NET_ADMIN \
  -p 10086:8006 \
  -p 13389:3389/tcp \
  -p 13389:3389/udp \
  --volume /srv/windows/data:/storage:z \
  --stop-timeout 300 \
  docker.io/dockurr/windows

Docker log

❯ Requesting Windows 11 from the Microsoft servers...
❯ Downloading Windows 11...
/storage/tmp/win11x64.iso                   100%[==========================================================================================>]   7.20G  61.4MB/s    in 2m 8s
❯ Extracting Windows 11 image...
❯ Adding drivers to image...
❯ Adding win11x64.xml for automatic installation...
❯ Building Windows 11 image...
❯ Creating a 100 GB growable disk image in raw format...
❯ Warning: Could not assign port 8006 to "USER_PORTS" because it is already in "HOST_PORTS"!
❯ Booting Windows using QEMU v10.0.3...
BdsDxe: skipped Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0)
BdsDxe: loading Boot0001 "UEFI QEMU DVD-ROM QM00013 " from PciRoot(0x0)/Pci(0x5,0x0)/Sata(0x0,0xFFFF,0x0)
BdsDxe: starting Boot0001 "UEFI QEMU DVD-ROM QM00013 " from PciRoot(0x0)/Pci(0x5,0x0)/Sata(0x0,0xFFFF,0x0)
❯ Windows started successfully, visit http://127.0.0.1:8006/ to view the screen...

Screenshots (optional)

vnc screen shot

[kroese]

Everything looks normal in your log/screenshots? So where did you see VNC say the boot was not found?

[kuyagic]

Everything looks normal in your log/screenshots? So where did you see VNC say the boot was not found?

vnc screen shot

the image first line. and then screen got freezed, not get into the installer progress.

the circle not moving. and freeze on boot

[kroese]

That line is normal, but the circle freezing is not. Does it also happen when you choose Win10 or Win7 for example?

[Microsoft-Maker1]

To fix the issue where the VNC screen shows "boot not found" despite the Podman logs indicating Windows started successfully, first stop and remove all existing containers using podman stop -a && podman rm -a, then delete the contents of your data directory with sudo rm -rf /srv/windows/data/* to ensure a clean rebuild. Re-run the container without the --rm flag so that data persists between runs, and make sure you're using the correct volume mount with SELinux context (--volume /srv/windows/data:/storage:z). After starting the container, wait for the message that Windows started successfully, and instead of using a VNC client, open a browser and visit http://localhost:8006 (or http://:10086 if accessing remotely) to view the Windows GUI, as dockurr/windows uses a web-based viewer instead of traditional VNC.

[kuyagic]

I tried to run the podman with the following command line and a clean /srv/window dir.

podman run -it \
  --name windows \
  --env VERSION="10" \
  --env DISK_SIZE="100G" \
  --env RAM_SIZE="8G" \
  --env CPU_CORES="4" \
  --env USERNAME="user" \
  --env PASSWORD="pass" \
  --env USER_PORTS="8006" \
  --env REGION="zh-CN" \
  --network dyweb \
  --device /dev/kvm:/dev/kvm \
  --device /dev/net/tun:/dev/net/tun \
  --cap-add NET_ADMIN \
  -p 10086:8006 \
  -p 13389:3389/tcp \
  -p 13389:3389/udp \
  --user root \
  --volume /srv/windows/data:/storage:z \
  --stop-timeout 15 \
  docker.io/dockurr/windows

the vnc shows the windows 10 boot screen is always circling infinitely, and can not boot into installer progress.