[Bug]: win7 failed cd-rom

[chspan]

Is there an existing issue for this?

• I have searched the existing issues

Machine specifications

Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz/16GB esxi virtual vm

Operating system

CentOS Linux release 7.9.2009 (Core)

Docker version

Docker version 24.0.7, build afdd53b

Description

The startup error is reported. Is it because the docker version is too low? The system has kvm virtualization.

Docker compose

version: "3"
services:
windows:
image: dockurr/windows
container_name: windows7
devices:

• /dev/kvm
  cap_add:
• NET_ADMIN
  ports:
• 8006:8006
• 3389:3389/tcp
• 3389:3389/udp
  stop_grace_period: 2m
  restart: on-failure
  environment:
  VERSION: "win7"

Docker log

[root@control-plane iso]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bb47dbb7833b dockurr/windows "/usr/bin/tini -s /r…" 18 seconds ago Up 17 seconds 0.0.0.0:3389->3389/tcp, :::3389->3389/tcp, 0.0.0.0:8006->8006/tcp, 0.0.0.0:3389->3389/udp, :::8006->8006/tcp, :::3389->3389/udp windows7
[root@control-plane iso]# docker logs bb47dbb7833b
❯ Starting Windows for Docker v3.03...
❯ For support visit https://github.com/dockur/windows
❯ CPU: Intel Xeon CPU E5 2620 v3 | RAM: 15/16 GB | DISK: 72 GB (xfs) | HOST: 3.10.0-1160.105.1.el7.x86_64...

❯ Booting Windows securely...
BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found
BdsDxe: failed to load Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0): Not Found
BdsDxe: No bootable option or device was found.
BdsDxe: Press any key to enter the Boot Manager Menu.
❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...

Screenshots (optional)

[kroese]

Looks like something wrong with the installation ISO. Can you show me the contents of the /storage folder?

[chspan]

version: "3"
services:
windows:
image: dockurr/windows
container_name: windows7
devices:
- /dev/kvm
cap_add:
- NET_ADMIN
ports:
- 8006:8006
- 3389:3389/tcp
- 3389:3389/udp
stop_grace_period: 2m
restart: on-failure
volumes:
- /data/dockur/win7/:/storage
environment:
VERSION: "win7" # 系统标识
CONSOLE: "Y"

is in /storage

[kroese]

When you switch from Windows versions above 7, to a version that is 7 or lower, you must always empty the /storage folder first.

So from Vista-->7 you dont need to do it, from 10-->11 you also dont need to do it, but from 11-->7 or 7-->11 always delete /storage or assign a fresh volume.

[chspan]

version: "3"
services:
windows:
image: dockurr/windows
container_name: windows7
devices:

• /dev/kvm
  cap_add:
• NET_ADMIN
  ports:
• 8006:8006
• 3389:3389/tcp
• 3389:3389/udp
  stop_grace_period: 2m
  restart: on-failure
  volumes:
• /data/dockur/win7/:/storage1
  environment:
  VERSION: "win7" # 系统标识
  CONSOLE: "Y"

Is it okay if you think about my new allocation like this?

[kroese]

No... You used /storage1 but it must be called /storage

[chspan]

Oh, you mean to ask me to delete the files in the directory /data/dockur/win7/ and re-download the test.

[kroese]

Change:

/data/dockur/win7/:/storage1

to

/data/dockur/win7:/storage

and delete all files in /data/dockur/win7

[chspan]

This is the effect after startup

[kroese]

Mmhh.. I remember that most people who had troubles with this container are using CentOS, so it might be some issue between CentOS and KVM.

Can you check if it helps when you add -e "HV=N" to disable Hyper-V enlightments?