Closed rogerdk closed 3 weeks ago
Strange.. I thought we had confirmation in #37 now that it works in Pi 5.
But this timeout is maybe a different issue, because that other one produced an error message about registers.
I dont have a clue why it hangs unfortunately :( I only tested this container on the Raspberry Pi 5 and there it worked fine.
At the beginning of #37 I was able to solve the:
❯ ERROR: qemu-system-aarch64: Failed to put registers after init: Invalid argument
but then I had the timout error.
I started the docker with bash
as entrypoint
and ran step by step the /run/entry.sh
to debug.
It seems to fail to start the tty
for the vnc
but I couldn't find any other log even though there was some CPU usage.
Although in the last 2 versions, after the timeout the container died.
bad luck I guess...
Yes, because I added this line to kill QEMU when there is no output for 15 seconds:
https://github.com/dockur/windows-arm/blob/7a5536eec79027c9a53262690e7f7a3958f26d5d/src/power.sh#L41
How did you find that it fails to start the TTY?
Because all that complicated code with pseudo-terminals is just so that I can launch QEMU in the background to be able to do graceful shutdown when the container stops. It can technically all be removed if needed.
Same error on Orange Pi 3B☹️
Same error on Raspberry Pi 4
Is this issue still present with the latest version (v2.18)?
Is this issue still present with the latest version (v2.18)?
Yes.
Should be fixed now in v2.20, it was confirmed that this version runs on the Orange Pi 5 Plus now.
Should be fixed now in v2.20, it was confirmed that this version runs on the Orange Pi 5 Plus now.
well, that's weird.
Operating system:
Ubuntu 22.04.4 LTS on OrangePi 3B
Compose File:
services:
windows:
container_name: windows
image: dockurr/windows-arm
environment:
VERSION: "win11"
devices:
- /dev/kvm
cap_add:
- NET_ADMIN
ports:
- 8006:8006
- 3389:3389/tcp
- 3389:3389/udp
stop_grace_period: 2m
Log:
windows | ❯ Starting Windows for Docker v2.20...
windows | ❯ For support visit https://github.com/dockur/windows-arm
windows | ❯ CPU: Cortex A55 | RAM: 6/8 GB | DISK: 853 GB (fuseblk) | HOST: 5.10.160-rockchip-rk356x...
windows |
windows | ❯ Warning: the filesystem of /storage is FUSE, this extra layer will negatively affect performance!
windows | ❯ ERROR: Samba daemon failed to start!
windows | invalid permissions on directory '/var/log/samba/cores': has 0777 should be 0700
windows | Failed to create /var/log/samba/cores for user 0 with mode 0700
windows | Unable to setup corepath for smbd: File exists
windows | smbd version 4.21.0-Debian-4.21.0+dfsg-1 started.
windows | Copyright Andrew Tridgell and the Samba Team 1992-2024
windows | invalid permissions on directory '/run/samba/msg.lock': has 0777 should be 0755
windows | ❯ Booting Windows using QEMU v9.1.0...
windows | ❯ ERROR: Timeout while waiting for QEMU to boot the machine!
windows | qemu-system-aarch64: terminating on signal 15 from pid 202 (<unknown process>)
windows | ❯ Shutdown completed!
windows exited with code 0
@Shaun-Fong I fixed it for the Pi 5 Plus, you have a 3B.
I am not sure what the problem is, but Im pretty sure that the 3B will not have enough power to run Windows in any case.
@Shaun-Fong I fixed it for the Pi 5 Plus, you have a 3B.
I am not sure what the problem is, but Im pretty sure that the 3B will not have enough power to run Windows in any case.
okay, thanks.
@kroese I am still experiencing timeouts. I started from zero but I have the same timeout problem. Do I have to have any specific configuration? Just to confirm, I have the OrangePI 5 Plus.
Operating system
Debian 12 on Orange Pi 5 Plus
Description
When starting docker I see the following error and it dies.
I was following the #37 issue but could not get past this timeout. however since version 2.09 it now dies after giving timeout. before it would hang with some CPU usage.
Docker compose
Docker log
Screenshots (optional)
No response