You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
❯ Extracting Windows 10 bootdisk...
❯ Extracting Windows 10 environment...
❯ Extracting Windows 10 setup...
❯ Extracting Windows 10 image...
❯ Adding drivers to image...
❯ Adding win10arm64.xml for automatic installation...
❯ Building Windows 10 image...
❯ Creating a 40G growable disk image in raw format...
❯ Booting Windows using QEMU v9.1.0...
me too,I tried using the automatically downloaded Win10 and Win11 images, but encountered a "start boot option" ,situation and am waiting for a solution
Docker log
windows | ❯ Starting Windows for Docker v2.20...
windows | ❯ For support visit https://github.com/dockur/windows-arm
windows | ❯ CPU: FTC663 | RAM: 12/16 GB | DISK: 128 GB (ext4) | HOST: 4.19.0-arm64-desktop...
windows |
windows | ❯ Booting Windows using QEMU v9.1.0...
❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...
Operating system
Debian kernel-4.19.0
Description
What is the reason for the container being stuck in the start boot option after startup
Docker compose
version: "3"
services:
windows:
image: dockurr/windows-arm
container_name: win10
environment:
VERSION: "win10"
CPU_CORES: "4"
RAM_SIZE: "4G"
DISK_SIZE: "40G"
LANGUAGE: "chinese"
privileged: true
devices:
- /dev/kvm
volumes:
- ./s-win10:/storage
# - ./win11arm64_zh.iso:/custom.iso
cap_add:
- NET_ADMIN
ports:
- 8006:8006
- 3389:3389/tcp
- 3389:3389/udp
stop_grace_period: 2m
Docker log
❯ Extracting Windows 10 bootdisk...
❯ Extracting Windows 10 environment...
❯ Extracting Windows 10 setup...
❯ Extracting Windows 10 image...
❯ Adding drivers to image...
❯ Adding win10arm64.xml for automatic installation...
❯ Building Windows 10 image...
❯ Creating a 40G growable disk image in raw format...
❯ Booting Windows using QEMU v9.1.0...
❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...
Screenshots (optional)
No response
The text was updated successfully, but these errors were encountered: