windows
windows copied to clipboard
Windows stuck at installer starting
I've tried Microsoft iso and custom iso but both get stuck here.
I've waited for several hours and it's still like this.
yml file
version: "3"
services:
windows:
image: dockurr/windows:latest
container_name: windows
devices:
- /dev/kvm
cap_add:
- NET_ADMIN
ports:
- 8006:8006
- 3389:3389/tcp
- 3389:3389/udp
- 48080:8080
- 48000:80
- 44443:443
stop_grace_period: 2m
restart: on-failure
environment:
MANUAL: "N"
VERSION: "2008"
RAM_SIZE: "8G"
CPU_CORES: "4"
DISK_SIZE: "500G"
volumes:
- /home/win:/storage
Do you only have this with Server 2008 or also with other versions?
Do you only have this with Server 2008 or also with other versions?
I tried win10 and the same problem occurred.
same problem
Maybe both of you can share some info about your system, so we can see if you have something in common. For example the same CPU, or the same OS, or certain kernel.
Because it would be a lot easier to find a solution as soon as we know under what circumstances it occurs.
Maybe both of you can share some info about your system, so we can see if you have something in common. For example the same CPU, or the same OS, or certain kernel.
Because it would be a lot easier to find a solution as soon as we know under what circumstances it occurs.
CPU: Intel(R) Xeon(R) CPU E5-2630 v2 OS: CentOS 7.5.1804 Kernel: 3.10.0-862.el7.x86_64 Docker: 23.0.6
I appreciate it.
My guess is that it has something to do with that Xeon CPU. Because the last time someone had strange failure during install was also with a Xeon CPU E5-2680 v4
It might be some CPU instruction that is missing (as that CPU was released 10 years ago) or some obscure bug in QEMU/KVM.
Things to try:
Disable emulation for the TPM module:
environment:
TPM: "N"
Disable Hyper-V enlightments:
environment:
HV: "N"
You can even disable KVM completely:
environment:
KVM: "N"
(Expect very low performance, but at least we know if it makes a difference or not)
CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz OS: CentOS 7.5.1804 Kernel: 3.10.0-862.el7.x86_64 Docker: 25.0.3
Okay, you both have CentOS 7.5.1804 and exactly the same kernel. That is a pretty big co-incidence, so then I think its not the CPU but something related to this version of CentOS.
However, its extremely difficult to figure out why QEMU does not work on that CentOS kernel. So my only suggestion would be to check if disabling Hyper-V in the compose file helps, otherwise I dont have many suggestions anymore.
I think this may be fixed now in v2.06