windows icon indicating copy to clipboard operation
windows copied to clipboard

Can't deploy a new VM anymore

Open EHRETic opened this issue 1 month ago • 2 comments

Operating system

Almalinux 9.7

Description

Hi there,

I wanted to spin a new VM this morning and I got stuck by (see container logs below)

Usually, I use a custom ISO but behavior is exactly the same and the ERRORs at the end will repeat too. It fails at "configuring boot" and then remote access will crash and lose it's IP.

Server is physical and up to date. Docker version is 1:29.0.2-1

Docker compose

services:
  windows:
    image: dockurr/windows
    container_name: mycontainername
    
    restart: unless-stopped

    environment:
      VERSION: '${VERSION}'
      #EDITION: '${EDITION}'
      LANGUAGE: '${LANGUAGE}'
      REGION: '${REGION}'
      KEYBOARD: '${KEYBOARD}'
      RAM_SIZE: '${RAM_SIZE}'
      CPU_CORES: '${CPU_CORES}'
      DISK_FMT: '${DISK_FMT}'
      DISK_SIZE: '${DISK_SIZE}'
      #DISK2_SIZE: '${DISK2_SIZE}'
      USERNAME: '${USERNAME}'
      PASSWORD: '${PASSWORD}'
      DHCP: '${DHCP}'
      #GPU: '${GPU}'
      #MANUAL: '${MANUAL}'
      
    volumes:
      - system:/storage
      #- data:/storage2
    
    devices:
      - /dev/kvm
      - /dev/vhost-net
      #- /dev/dri/renderD128:/dev/dri/renderD128

    device_cgroup_rules:
      - 'c *:* rwm'
    
    cap_add:
      - NET_ADMIN
    
    stop_grace_period: 2m
    
    networks:
      default:
        ipv4_address: 192.168.X.Y

volumes:
  system:
  #data:

networks:
  default:
    external: true
    name: clients

Variables: VERSION=11 EDITION=core LANGUAGE=French REGION=fr-FR KEYBOARD=de-CH RAM_SIZE=4G CPU_CORES=2 DISK_FMT=qcow2 DISK_SIZE=128G DISK2_SIZE=30G USERNAME=User PASSWORD=Password DHCP=Y GPU=Y MANUAL=Y

Docker log

❯ Starting Windows for Docker v5.13...
❯ For support visit https://github.com/dockur/windows
❯ CPU: Intel Core Ultra 9 285K | RAM: 184/249 GB | DISK: 2 TB (xfs) | KERNEL: 5.14.0-611.5.1.el9_7.x86_64...
❯ Detected that your custom .iso file was removed, a backup of your previous installation will be saved...
❯ Requesting Windows 11 in French from the Microsoft servers...
❯ ERROR: Failed to contact Microsoft servers! Is there an Internet connection or is the server down?
❯ Will retry in 5 seconds...
❯ Requesting Windows 11 in French from the Microsoft servers...
❯ ERROR: Failed to contact Microsoft servers! Is there an Internet connection or is the server down?
❯ Failed to download Windows 11 in French, will try a different method now...
❯ Downloading catalog...
❯ Downloading Windows 11 in French...
     0K ........ ........ ........ ........  0%  125M 35s

----

4554752K ........ ........ .......          100%  166M=28s
❯ Extracting Windows 11 bootdisk...
❯ Extracting Windows 11 environment...
❯ Extracting Windows 11 setup...
❯ Extracting Windows 11 image...
❯ Adding drivers to image...
❯ Adding win11x64.xml for automatic installation...
❯ Building Windows 11 image...
❯ Creating a 128 GB growable disk image in qcow2 format...
Formatting '/storage/data.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=off compression_type=zlib size=137438953472 lazy_refcounts=off refcount_bits=16
2025/11/21 10:06:53 [fiano][FATAL] exit status 1
❯ ERROR: Status 1 while: /run/utk.bin "$OVMF/$ROM" replace_ffs LogoDXE "/var/www/img/${PROCESS,,}.ffs" save "$DEST.tmp" (line 79/22)
❯ Starting Windows for Docker v5.13...
❯ For support visit https://github.com/dockur/windows
❯ CPU: Intel Core Ultra 9 285K | RAM: 183/249 GB | DISK: 2 TB (xfs) | KERNEL: 5.14.0-611.5.1.el9_7.x86_64...
2025/11/21 10:06:54 [fiano][FATAL] exit status 1
❯ ERROR: Status 1 while: /run/utk.bin "$OVMF/$ROM" replace_ffs LogoDXE "/var/www/img/${PROCESS,,}.ffs" save "$DEST.tmp" (line 79/22)
❯ Starting Windows for Docker v5.13...
❯ For support visit https://github.com/dockur/windows
❯ CPU: Intel Core Ultra 9 285K | RAM: 184/249 GB | DISK: 2 TB (xfs) | KERNEL: 5.14.0-611.5.1.el9_7.x86_64...

etc...

Screenshots (optional)

No response

EHRETic avatar Nov 21 '25 10:11 EHRETic

I dont know exactly what is causing this error, but in the mean time you can workaround it by setting

 environment:
      LOGO: "N"

kroese avatar Nov 21 '25 11:11 kroese

I dont know exactly what is causing this error, but in the mean time you can workaround it by setting

environment: LOGO: "N"

Yes, it worked great, thanks a lot! 😉👌 If you want me to test a few things to try figuring out why, let me know what to do.

EHRETic avatar Nov 21 '25 11:11 EHRETic