Install or extract do not finish in docker, with mcr.microsoft.com/windows/servercore:2009-amd64
See original GitHub issueBoth installer and tarball fail to fully install in docker.
The installer does extract partially, but is missing bash.exe and pacman.exe For the installer, I am running:
Invoke-WebRequest https://github.com/msys2/msys2-installer/releases/download/2022-01-18/msys2-base-x86_64-20220118.sfx.exe -Outfile C:\tools\msys-setup.exe;
Start-Process "C:\tools\msys-setup.exe" -ArgumentList "-y -oC:\ " -Wait
The tarball extracts more, including bash.exe but is missing pacman.exe. For the tarball, I am running:
Invoke-WebRequest http://repo.msys2.org/distrib/msys2-x86_64-latest.tar.xz -Outfile C:\tools\msys2.tar.xz
Start-process "7z" -ArgumentList "e C:\tools\msys2.tar.xz -oC:\tools " -NoNewWindow -Wait
Start-process "7z" -ArgumentList "x C:\tools\msys2.tar -oC:\ " -NoNewWindow -Wait
I have tried running docker ‘build’ and docker ‘run’:
docker build --memory 2GB --isolation process --build-arg BASE_TAG=$BASE_TAG --tag $TAG $COMPOSE_DIR
docker run -it --memory 2GB --isolation process docker-virtual.artifactory.york.lan/windows/servercore:2009-amd64 powershell
Wonder if it’s due to permissions or antivirus (Carbon Black or Endpoint Protector).
I have tried other installers:
https://github.com/msys2/msys2-installer/releases/download/nightly-x86_64/msys2-base-x86_64-latest.sfx.exe
https://github.com/msys2/msys2-installer/releases/download/nightly-x86_64/msys2-x86_64-latest.exe
And other tarballs:
https://github.com/msys2/msys2-installer/releases/download/nightly-x86_64/msys2-base-x86_64-latest.tar.xz
This was running for us with previous Windows versions, 1809-amd64 and 1909-amd64.
Issue Analytics
- State:
- Created 10 months ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
You might encounter issues when using Windows Server ...
When you run the command "docker run" or “docker build” you might not receive output and it might become non-responsive. Your Windows Server ......
Read more >Install on Windows | Docker Documentation
Install from the command line --admin-settings : Automatically creates an admin-settings. json file which is used by admins to control certain Docker Desktop ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@relapids please open a new issue (and just copy what you posted here)
Same thing started happening to me yesterday with no changes on my end (been working for months up until now). Was definitely working two days ago since I have a script to force-rebuild my image daily. I see this on multiple machines and OS versions.
Tried both isolation modes (hyperv and process) and neither are currently working for me. One slight difference to the original reporter is that I’m using servercore:ltsc2022.
Still trying to diagnose further but unfortunately it’s difficult to get diagnostic information from Windows containers for these sorts of issues. Trying to investigate using the information here: https://learn.microsoft.com/en-us/virtualization/windowscontainers/troubleshooting
EDIT:
Actually, I think I may have misunderstood the original issue in this thread and conflated it with mine. In my case the processes all appear to run successfully and terminate normally, but then the RUN step never finishes and just hangs indefinitely when finalizing the layer. I’m guessing this is probably a distinct issue and I misclassified it as the same as the one here due to the timing.
Strange though that it’s happening on multiple machines and seems to coincide with the latest installer release. I tried rolling back to an earlier installer but that didn’t help. Likely because whatever is causing the issue gets updated to the same version as in the latest installer anyway, but that’s just a guess on my part so far - I need to do additional testing.