Error on Extract ESD about windows

[lostx754]

using portainer I deleted the container and the image, and then I removed the parameter that deletes the container after shutdown (--rm) and removed -it and added the ram parameter as 1gb (as my system would work better) and tested Firstly in XP it worked

[kroese]

Mmhh.. interesting! I just tried it and I cannot reproduce this. Both our ESD files 4.54G so I am pretty sure Microsoft is serving us the same file.

Are you sure you didnt press any key by accident? Because I see this strange line 3353 Killed wimlib-imagex so if you press CTRL+C for example it will kill the extraction process and it is logical that it fails.

[kroese]

Okay after some experimenting I see that it doesnt get killed by a keypress, so I am pretty sure the extraction gets killed because the process runs out of RAM on your machine.

Is it possible that you are low on memory?

[lostx754]

I will investigate, please don't close my issue

and the arm version returned this for me:

root@Lost:/home/lost# docker run -it --rm -p 8006:8006 --device=/dev/kvm --cap-add NET_ADMIN --stop-timeout 120 dockurr/windows-arm
Unable to find image 'dockurr/windows-arm:latest' locally
latest: Pulling from dockurr/windows-arm
d8262e50bff0: Pull complete
5f9aee76f191: Pull complete
2df91a0534ce: Pull complete
680913de3157: Pull complete
80057ec7d929: Pull complete
e63aa8673fa5: Pull complete
0bf25f7fa3ba: Pull complete
95624becc3ce: Pull complete
Digest: sha256:fbf2e68b1f50ead09877bc4bfdb13ae4394bf0a55a09d481ca1028ab91d10d88
Status: Downloaded newer image for dockurr/windows-arm:latest
❯ Starting Windows for Docker v1.07...
❯ For support visit https://github.com/dockur/windows-arm

❯ Downloading product information from Microsoft...
❯ Downloading Windows 11 for ARM...
/storage/tmp/win11arm64.esd 100%[=================================================================>] 4.88G 11.9MB/s in 7m 3s
❯ Extracting Windows 11 for ARM bootdisk...
❯ Extracting Windows 11 for ARM environment...
❯ Extracting Windows 11 for ARM setup...
❯ Extracting Windows 11 for ARM image...
❯ Adding XML file for automatic installation...
❯ Building Windows 11 for ARM image...
❯ Creating a 64G growable disk image in raw format...
❯ Booting Windows using QEMU emulator version 8.2.1 ...
❯ ERROR: qemu-system-aarch64: cannot set up guest memory 'mach-virt.ram': Cannot allocate memory

[kroese]

Yes also the ARM version complains about not being able to allocate RAM. So it really looks like there is a problem for Docker to have enough memory on your device. How much RAM do you have?

[lostx754]

I have 4 gigs but I've already run vm through virtual box on this pc with this configuration ;-;

[lostx754]

and my cpu arch is x86_64

[kroese]

If your CPU is x86 then you should not run the ARM version of Windows because its not for x86 CPU's.

You can lower the amount of RAM in the compose file by setting

environment:
  RAM_SIZE: "2G"

for example. But this only lowers the RAM for Windows, and you already have RAM shortage while extracting the ESD file, so it will not help in your case Im afraid.

[lostx754]

how can I add this to the docker command? (i use ubuntu)

[lostx754]

If I have 8GB of RAM, would it run the same if I limited the container to 2 or 4GB?

[kroese]

By adding:

-e "RAM_SIZE=2G"

to the run command. But this is the RAM that Windows is allowed to use, but you already have the problem before Windows even starts, so it will not help your case.

The only workaround for you would be to download the ISO manually and save it as custom.iso in the /storage folder so it does not need to extract ESD files. And then start Windows with 2GB of RAM, but it will not be a good experience as Windows 11 expects a better system.

I think it was better that you choose Windows 7 for example.

[lostx754]

how i can use the windows 7?

[kroese]

https://github.com/dockur/windows#how-do-i-select-the-windows-version

An alternative would be to choose core11 or tiny11 because those are Windows 11 versions that require less RAM because of less bloatware.

[lostx754]

same error

[lostx754]

The error even occurred with XP

[kroese]

But you did not change the amount of RAM in the run command, and by default its 4GB which is impossible on your system as it has 4GB in total.

[lostx754]

i can use -e "RAM_SIZE=2G" ?

[kroese]

Yes or 1G for 1GB

[lostx754]

it booted (from vnc) and soon after it disconnected

[kroese]

Without posting your run command + the log it will be impossible to tell what happened, I can see only 1 line in the screenshot.

[lostx754]

The next line was my next command where I had started the container, but I already solved the problem, congratulations on the project my friend <3

[kroese]

If you could explain what you did to solve it then other people reading this issue in the future could learn from that.