Error while building on windows finding micaut.dll.mui

[revantjhalani]

I tried building on a newly installed windows but I got the same error so I reinstalled the older 1809 as asked for, but the same error persists. Here's what the output looks like:

PS C:\Windows\system32> docker pull ultimaker/cura-build-environment
Using default tag: latest
latest: Pulling from ultimaker/cura-build-environment
75f829a71a1c: Pull complete
000f65b344e8: Pull complete
bceaaf80f4a6: Pull complete
f69296dd68b2: Pull complete
633267254979: Pull complete
dcca9bf457cc: Pull complete
cbfd56246533: Pull complete
Digest: sha256:098fc04a4f18437b037f157be888a06fb0c3a3b07db1548a044c9083fb197806
Status: Downloaded newer image for ultimaker/cura-build-environment:latest
docker.io/ultimaker/cura-build-environment:latest
PS C:\Windows\system32> cd C:\Users\howler\cura\cura-build-environment\
PS C:\Users\howler\cura\cura-build-environment> docker build -t build-env -f docker/windows/Dockerfile.vs2015 .
[+] Building 229.4s (5/14)
 => [internal] load build definition from Dockerfile.vs2015                                                                                                                                         0.1s
 => => transferring dockerfile: 2.37kB                                                                                                                                                              0.0s
 => [internal] load .dockerignore                                                                                                                                                                   0.1s
 => => transferring context: 47B                                                                                                                                                                    0.0s
 => [internal] load metadata for mcr.microsoft.com/windows/servercore:1809-amd64                                                                                                                    2.0s
 => ERROR [ 1/10] FROM mcr.microsoft.com/windows/servercore:1809-amd64@sha256:ea59e234726dc50e67b67ec14eb77fc96094dbce61c71f2bda6e82b8caf787aa                                                    227.2s
 => => resolve mcr.microsoft.com/windows/servercore:1809-amd64@sha256:ea59e234726dc50e67b67ec14eb77fc96094dbce61c71f2bda6e82b8caf787aa                                                              0.0s
 => => sha256:ea59e234726dc50e67b67ec14eb77fc96094dbce61c71f2bda6e82b8caf787aa 886B / 886B                                                                                                          0.0s
 => => sha256:5c1f582f60a9895cf4d66595d265ec88225efd6a33e90edfd1a2ff161991ce50 559B / 559B                                                                                                          0.0s
 => => sha256:4612f6d0b889cad0ed0292fae3a0b0c8a9e49aff6dea8eb049b2386d9b07986f 1.72GB / 1.72GB                                                                                                    174.7s
 => => sha256:aa4f58cd6da1aaf1a0b44d443bd88e7fbe5b0a6f193995a1a61d6bd63990f314 672.54MB / 672.54MB                                                                                                 57.1s
 => => extracting sha256:4612f6d0b889cad0ed0292fae3a0b0c8a9e49aff6dea8eb049b2386d9b07986f                                                                                                          40.2s
 => => extracting sha256:aa4f58cd6da1aaf1a0b44d443bd88e7fbe5b0a6f193995a1a61d6bd63990f314                                                                                                          10.6s
 => [internal] load build context                                                                                                                                                                   0.1s
 => => transferring context: 117.25kB                                                                                                                                                               0.0s
------
 > [ 1/10] FROM mcr.microsoft.com/windows/servercore:1809-amd64@sha256:ea59e234726dc50e67b67ec14eb77fc96094dbce61c71f2bda6e82b8caf787aa:
------
failed to register layer: Error processing tar file(exit status 1): link /Files/Program Files/common files/Microsoft Shared/Ink/en-US/micaut.dll.mui /Files/Program Files (x86)/common files/Microsoft Shared/ink/en-US/micaut.dll.mui: no such file or directory
-----

The path seems kinda weird. Not sure how I should go about this

[nallath]

I can find some other people who are trying to build other applications who have the same problem, but no-one really seems to have a fix for it.

I've never seen the issue myself...

[Ghostkeeper]

Yeah the Windows docker image was really never finished. I think the DevOps guy at the time got it to work at some point but it wasn't integrated in the CI suite yet because it required manual handywork. But nobody knows how to get it to work any more.

Should we remove that Windows image to prevent confusion?

[revantjhalani]

I see, that's unfortunate. Yeah, I guess it'd be better if it is removed if it does not work at all and if there are no future plans to make it work. Just wanted to ask, the command is correct, right? docker build -t build-env -f docker/windows/Dockerfile.vs2015 . I ran into some confusion regarding the "tag"

[evtrados]

The problem with the Windows docker image is that (from what I've also read online), it's really hard to get it working natively, unless you have a Windows Server 1809 machine. For all other windows versions it will fail at some stage. It is, however, used in our alternative CI suite and is working without issues. But that is because we always use a 1809 Windows server VM to build Cura.

Regarding your question: yes, you can use whatever name you want in your tag, so the command is correct.

[revantjhalani]

@evtrados Hey, thanks for the reply, so I tried out the exact same process on an 1809 Windows server VM, ran into the exact same issue again. `

---

PS C:\Users\Administrator\cura\cura-build-environment> docker build -t howler-build -f docker/windows/Dockerfile.vs2015 . [+] Building 209.8s (5/14) => [internal] load build definition from Dockerfile.vs2015 0.0s => => transferring dockerfile: 39B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 34B 0.0s => [internal] load metadata for mcr.microsoft.com/windows/servercore:1809-amd64 1.2s => ERROR [ 1/10] FROM mcr.microsoft.com/windows/servercore:1809-amd64@sha256:ea59e234726dc50e67b67ec14eb77fc96094dbce61c71f2bda6e82b8caf787aa 208.5s => => resolve mcr.microsoft.com/windows/servercore:1809-amd64@sha256:ea59e234726dc50e67b67ec14eb77fc96094dbce61c71f2bda6e82b8caf787aa 0.0s => => sha256:ea59e234726dc50e67b67ec14eb77fc96094dbce61c71f2bda6e82b8caf787aa 886B / 886B 0.0s => => sha256:5c1f582f60a9895cf4d66595d265ec88225efd6a33e90edfd1a2ff161991ce50 559B / 559B 0.0s => => sha256:4612f6d0b889cad0ed0292fae3a0b0c8a9e49aff6dea8eb049b2386d9b07986f 1.72GB / 1.72GB 134.6s => => sha256:aa4f58cd6da1aaf1a0b44d443bd88e7fbe5b0a6f193995a1a61d6bd63990f314 672.54MB / 672.54MB 0.0s => => extracting sha256:4612f6d0b889cad0ed0292fae3a0b0c8a9e49aff6dea8eb049b2386d9b07986f 57.7s => => extracting sha256:aa4f58cd6da1aaf1a0b44d443bd88e7fbe5b0a6f193995a1a61d6bd63990f314 15.4s => [internal] load build context 0.0s => => transferring context: 2.54kB 0.0s

[ 1/10] FROM mcr.microsoft.com/windows/servercore:1809-amd64@sha256:ea59e234726dc50e67b67ec14eb77fc96094dbce61c71f2bda6e82b8caf787aa:

failed to register layer: Error processing tar file(exit status 1): link /Files/Program Files/common files/Microsoft Shared/Ink/en-US/micaut.dll.mui /Files/Program Files (x86)/common files/Microsoft Shared/ink/en-US/micaut.dll.mui: no such file or directory

`

Pretty sure I did everything right including the windows version, and it's also a server now. Here is the version info, it's the exact same as the on in the readme: `

PS C:\Users\Administrator> [System.Environment]::OSVersion.Version

Major Minor Build Revision

---

10 0 17763 0

`

P.S.: Not sure if that's okay for you since it might be a lot of effort, but by any chance could you upload the working VM that you mentioned? I have a server, I could give you storage space for you to upload the image to in case it's too big

[Gornerrrrr]

also same problem :(

[shrumit]

Building on Windows and faced the same error. What solved it for me was to right-click on the Docker icon in the taskbar and click "Switch to Windows containers...". I've also unchecked "Use the WSL 2 based engine" in the settings.

[Robert-Legrand]

I tryed to build on Unbuntu WSL2 and Windows powershell. I got the same link problems after disabling all WSL parameters in the last version of Docker Desktop and under Powershell :

failed to register layer:Error processing tar file(exit status 1): link /Files/Program Files/common files/Microsoft Shared/Ink/en-US/micaut.dll.mui /Files/Program Files (x86)/common files/Microsoft Shared/ink/en-US/micaut.dll.mui: no such file or directory

The files are présent in my Windows path but can't be adressed with a /Files/Program Files/ ... in Windows (c:\Program Files) or in Ubuntu WSL2 (/mnt/c/Program Files/).

[JLouisDev]

shrumit's answer fixed the issue for me as well, but for a different program.