`choco install` fails with `Exit code was '-2147023829'` on a Windows 11 host with process isolation

[TomSmithGR]

Output of the ue4-docker info command:

PS D:\ue4docker> ue4-docker info
ue4-docker version: 0.0.94 (latest available version is 0.0.94)
Operating system: Windows 10 Pro (Build 22000.376)
Docker daemon version: 20.10.11
NVIDIA Docker supported: No
Maximum image size: 400GB
Available disk space: 6.7 TiB
Total system memory: 255.83 GiB physical, 293.83 GiB virtual
Number of processors: 64 physical, 128 logical

Additional details:

• Are you accessing the network through a proxy server? NO

I am running windows 11 as a host OS.

I am building using the following command:
PS D:\ue4docker> ue4-docker build -username redacted -password redacted --exclude ddc -basetag ltsc2022 -isolation=process --visual-studio=2019 4.27.2

The build is failing to create the prerequisites image, when installing git from chocolatey.
ERROR: Running ["C:\ProgramData\chocolatey\lib\git.install\tools\Git-2.34.1-64-bit.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /NOCANCEL /SP- /LOG /COMPONENTS="icons,assoc,assoc_sh,,,,gitlfs,icons\quicklaunch" /o:PathOption=Cmd /o:BashTerminalOption=ConHost /o:CRLFOption=CRLFCommitAsIs ] was not successful. Exit code was '-1073741819'. See log for possible error messages.

I tried creating a ltsc2022 windows server container, and repeated the following command:
choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"

git installed successfully during that attempt, so this does not appear to be a chocolatey issue.

I have repeated the ue4-docker build several times, and get the same result.
ue4-docker build log.txt
chocolatey.log

[TBBle]

That's an access violation (0xc0000005), which is a super-weird thing to happen, and certainly shouldn't be caused by any of the things done to create the container...

If you run the container image as it stood before that step (d3f3e304f75d in your attached build log), and run the same choco install command again, does it fail?

If so, then something done earlier in the image build has corrupted the system weirdly, but since all that has been done is copy some DLLs, enable long paths, and install chocolately, I can't see what it would be.

If not, then something in how ue4-docker is starting the container must be different from when it's run by hand.

Was your stand-alone test also using process isolation, by the way? It's not the default for docker run on client Windows builds.

[TomSmithGR]

Hi, thanks for looking into this, you are right, I must have not specified isolation during my initial test. I have now repeated some testing, and it appears that the issue occurs on both server core and prerequisites containers when running in process isolation, but not with the default isolation behaviour.

Test1: Existing prerequisites container

I create a container from the image as it stood before the last step using the following command:
docker create --isolation=process --interactive d3f3e304f75d
I manually execute the command:

'choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"'

The result is:
`C:\>choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"
choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"
Chocolatey v0.11.3
Installing the following packages:
git
By installing, you accept licenses for the packages.
Progress: Downloading git.install 2.34.1... 100%
Progress: Downloading chocolatey-core.extension 1.3.5.1... 100%
Progress: Downloading git 2.34.1... 100%

chocolatey-core.extension v1.3.5.1 [Approved]
chocolatey-core.extension package files install completed. Performing other installation steps.
 Installed/updated chocolatey-core extensions.
 The install of chocolatey-core.extension was successful.
  Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-core'

git.install v2.34.1 [Approved]
git.install package files install completed. Performing other installation steps.
Parameter: no git shell integration
Using Git LFS
Installing 64-bit git.install...
ERROR: Running ["C:\ProgramData\chocolatey\lib\git.install\tools\Git-2.34.1-64-bit.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /NOCANCEL /SP- /LOG /COMPONENTS="icons,assoc,assoc_sh,,,,gitlfs,icons\quicklaunch" /o:PathOption=Cmd /o:BashTerminalOption=ConHost /o:CRLFOption=CRLFCommitAsIs ] was not successful. Exit code was '-1073741819'. See log for possible error messages.
The install of git.install was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\git.install\tools\chocolateyInstall.ps1'.
 See log for details.

git v2.34.1 [Approved]
git package files install completed. Performing other installation steps.
 The install of git was successful.
  Software install location not explicitly set, it could be in package or
  default install location of installer.

Chocolatey installed 2/3 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - git.install (exited -1073741819) - Error while running 'C:\ProgramData\chocolatey\lib\git.install\tools\chocolateyInstall.ps1'.
 See log for details.`
### Test 2: server core container with process isolation
Next I repeat the process with server core:
'mcr.microsoft.com/windows/servercore   ltsc2022   136110e1a05c   4 weeks ago    4.91GB'

'docker create --isolation=process --interactive 136110e1a05c
docker start bf9e8e81f63baa5d67d10d4d01c3105e3f3952f16f04be2cf05d5aa35fed72ee
docker attach bf9e8e81f63baa5d67d10d4d01c3105e3f3952f16f04be2cf05d5aa35fed72ee'

I install chocolatey using powerscript, and run the command again:
'C:\>powershell
powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\> Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
Forcing web requests to allow TLS v1.2 (Required for requests to Chocolatey.org)
Getting latest version of the Chocolatey package for download.
Not using proxy.
Getting Chocolatey from https://community.chocolatey.org/api/v2/package/chocolatey/0.11.3.
Downloading https://community.chocolatey.org/api/v2/package/chocolatey/0.11.3 to C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip
Not using proxy.
Extracting C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip to C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall
Installing Chocolatey on the local machine
Creating ChocolateyInstall as an environment variable (targeting 'Machine')
  Setting ChocolateyInstall to 'C:\ProgramData\chocolatey'
WARNING: It's very likely you will need to close and reopen your shell
  before you can use choco.
Restricting write permissions to Administrators
We are setting up the Chocolatey package repository.
The packages themselves go to 'C:\ProgramData\chocolatey\lib'
  (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin'
  and points to an executable in 'C:\ProgramData\chocolatey\lib\yourPackageName'.

Creating Chocolatey folders if they do not already exist.

WARNING: You can safely ignore errors related to missing log files when
  upgrading from a version of Chocolatey less than 0.9.9.
  'Batch file could not be found' is also safe to ignore.
  'The system cannot find the file specified' - also safe.
chocolatey.nupkg file not installed in lib.
 Attempting to locate it from bootstrapper.
PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...
WARNING: Not setting tab completion: Profile file does not exist at
'C:\Users\ContainerAdministrator\Documents\WindowsPowerShell\Microsoft.PowerShe
ll_profile.ps1'.
Chocolatey (choco.exe) is now ready.
You can call choco from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles
 first prior to using choco.
Ensuring Chocolatey commands are on the path
Ensuring chocolatey.nupkg is in the lib folder
PS C:\> choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"
choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"
Chocolatey v0.11.3
Installing the following packages:
git
By installing, you accept licenses for the packages.
Progress: Downloading git.install 2.34.1... 100%
Progress: Downloading chocolatey-core.extension 1.3.5.1... 100%
Progress: Downloading git 2.34.1... 100%

chocolatey-core.extension v1.3.5.1 [Approved]
chocolatey-core.extension package files install completed. Performing other installation steps.
 Installed/updated chocolatey-core extensions.
 The install of chocolatey-core.extension was successful.
  Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-core'

git.install v2.34.1 [Approved]
git.install package files install completed. Performing other installation steps.
Parameter: no git shell integration
Using Git LFS
Installing 64-bit git.install...
ERROR: Running ["C:\ProgramData\chocolatey\lib\git.install\tools\Git-2.34.1-64-bit.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /NOCANCEL /SP- /LOG /COMPONENTS="icons,assoc,assoc_sh,,,,gitlfs,icons\quicklaunch" /o:PathOption=Cmd /o:BashTerminalOption=ConHost /o:CRLFOption=CRLFCommitAsIs ] was not successful. Exit code was '-1073741819'. See log for possible error messages.
The install of git.install was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\git.install\tools\chocolateyInstall.ps1'.
 See log for details.

git v2.34.1 [Approved]
git package files install completed. Performing other installation steps.
 The install of git was successful.
  Software install location not explicitly set, it could be in package or
  default install location of installer.

Chocolatey installed 2/3 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - git.install (exited -1073741819) - Error while running 'C:\ProgramData\chocolatey\lib\git.install\tools\chocolateyInstall.ps1'.
 See log for details.
PS C:\>'

Test 3: server core with default isolation

Creating the same image, but without specifying process isolation:

'docker create --interactive 136110e1a05c
docker start 52442b3743bd5b24829e3b43520b5e67954dc28babf03b95087c9a2aa8609b9c
docker attach 52442b3743bd5b24829e3b43520b5e67954dc28babf03b95087c9a2aa8609b9c'

'C:\>powershell
powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\> Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
Forcing web requests to allow TLS v1.2 (Required for requests to Chocolatey.org)
Getting latest version of the Chocolatey package for download.
Not using proxy.
Getting Chocolatey from https://community.chocolatey.org/api/v2/package/chocolatey/0.11.3.
Downloading https://community.chocolatey.org/api/v2/package/chocolatey/0.11.3 to C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip
Not using proxy.
Extracting C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip to C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall
Installing Chocolatey on the local machine
Creating ChocolateyInstall as an environment variable (targeting 'Machine')
  Setting ChocolateyInstall to 'C:\ProgramData\chocolatey'
WARNING: It's very likely you will need to close and reopen your shell
  before you can use choco.
Restricting write permissions to Administrators
We are setting up the Chocolatey package repository.
The packages themselves go to 'C:\ProgramData\chocolatey\lib'
  (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin'
  and points to an executable in 'C:\ProgramData\chocolatey\lib\yourPackageName'.

Creating Chocolatey folders if they do not already exist.

WARNING: You can safely ignore errors related to missing log files when
  upgrading from a version of Chocolatey less than 0.9.9.
  'Batch file could not be found' is also safe to ignore.
  'The system cannot find the file specified' - also safe.
chocolatey.nupkg file not installed in lib.
 Attempting to locate it from bootstrapper.
PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...
WARNING: Not setting tab completion: Profile file does not exist at
'C:\Users\ContainerAdministrator\Documents\WindowsPowerShell\Microsoft.PowerShe
ll_profile.ps1'.
Chocolatey (choco.exe) is now ready.
You can call choco from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles
 first prior to using choco.
Ensuring Chocolatey commands are on the path
Ensuring chocolatey.nupkg is in the lib folder
PS C:\> choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"
choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"
Chocolatey v0.11.3
Installing the following packages:
git
By installing, you accept licenses for the packages.
Progress: Downloading git.install 2.34.1... 100%
Progress: Downloading chocolatey-core.extension 1.3.5.1... 100%
Progress: Downloading git 2.34.1... 100%

chocolatey-core.extension v1.3.5.1 [Approved]
chocolatey-core.extension package files install completed. Performing other installation steps.
 Installed/updated chocolatey-core extensions.
 The install of chocolatey-core.extension was successful.
  Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-core'

git.install v2.34.1 [Approved]
git.install package files install completed. Performing other installation steps.
Parameter: no git shell integration
Using Git LFS
Installing 64-bit git.install...
git.install has been installed.
WARNING: Can't find git.install install location
  git.install can be automatically uninstalled.
Environment Vars (like PATH) have changed. Close/reopen your shell to
 see the changes (or in powershell/cmd.exe just type `refreshenv`).
 The install of git.install was successful.
  Software installed to 'C:\Program Files\Git\'

git v2.34.1 [Approved]
git package files install completed. Performing other installation steps.
 The install of git was successful.
  Software install location not explicitly set, it could be in package or
  default install location of installer.

Chocolatey installed 3/3 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
PS C:\>'

Test4: reinstalling git on process isolation windows core container

Connecting back to the process isolation container with windows core, I then started to investigate how the installer fails.
I noticed that despite the failure, the container has a working copy of git installed.

I ran the following command to pull a fresh copy of the installer:

'Invoke-WebRequest -Uri https://github.com/git-for-windows/git/releases/download/v2.34.1.windows.1/Git-2.34.1-64-bit.exe -OutFile ./Git-2.34.1-64-bit.exe'

Then i manually uninstalled git:
"%ProgramFiles%\Git\unins000.exe" /VERYSILENT /NORESTART

then running the installer with a log file specified:
'C:\>Git-2.34.1-64-bit.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /NOCANCEL /SP- /LOG="c:\test2.log" /COMPONENTS="icons,assoc,assoc_sh,,,,gitlfs,icons\quicklaunch" /o:PathOption=Cmd /o:BashTerminalOption=ConHost /o:CRLFOption=CRLFCommitAsIs'

Log appears to show a successful install, i will repeat this process on a fresh image and see if I can get it to fall over.
test2.log

[TomSmithGR]

Ok, manually downloading and installing git on a fresh windows core container with process isolation appears to work fine. The install completes without any errors.

Looking at the containers where installs fail, they still end up with working copies of Git installed, so something must be causing the installer to fail late in the install process. As this is happening both on server core and prerequisites containers when installing with chocolatey, but succeeds when installed manually on server core, I would assume the cause of the issue is likely to do with the chocolatey installer package.

Test5: install git on new server core image with process isolation

D:\ue4docker>docker create --isolation=process --interactive 136110e1a05c
fd75a9adc012bcfbd397ec52a656a6f31250892ddf4ef0b1d73ff766021434c5

D:\ue4docker>docker start fd75a9adc012bcfbd397ec52a656a6f31250892ddf4ef0b1d73ff766021434c5
fd75a9adc012bcfbd397ec52a656a6f31250892ddf4ef0b1d73ff766021434c5

D:\ue4docker>docker attach fd75a9adc012bcfbd397ec52a656a6f31250892ddf4ef0b1d73ff766021434c5
powershell
powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\> Invoke-WebRequest -Uri https://github.com/git-for-windows/git/releases/download/v2.34.1.windows.1/Git-2.34.1-64-bit.exe -OutFile ./Git-2.34.1-64-bit.exe
Invoke-WebRequest -Uri https://github.com/git-for-windows/git/releases/download/v2.34.1.windows.1/Git-2.34.1-64-bit.exe -OutFile ./Git-2.34.1-64-bit.exe
PS C:\> exit
exit

C:\>Git-2.34.1-64-bit.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /NOCANCEL /SP- /LOG="c:\test.log" /COMPONENTS="icons,assoc,assoc_sh,,,,gitlfs,icons\quicklaunch" /o:PathOption=Cmd /o:BashTerminalOption=ConHost /o:CRLFOption=CRLFCommitAsIs
Git-2.34.1-64-bit.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /NOCANCEL /SP- /LOG="c:\test.log" /COMPONENTS="icons,assoc,assoc_sh,,,,gitlfs,icons\quicklaunch" /o:PathOption=Cmd /o:BashTerminalOption=ConHost /o:CRLFOption=CRLFCommitAsIs

Log file:
test.log

[TBBle]

I'm suspicious of that "success" even in the Hyper-V isolation mode, due to

WARNING: Can't find git.install install location

which comes from the second-last line of this snippet from the install script, where the first line in the snippet is the failing line in process isolation:

Install-ChocolateyInstallPackage @packageArgs
Get-ChildItem $toolsPath\$fileName32, $toolsPath\$fileName64 | ForEach-Object { Remove-Item $_ -ea 0; if (Test-Path $_) { Set-Content "$_.ignore" '' } }

$packageName = $packageArgs.packageName
$installLocation = Get-AppInstallLocation $packageArgs.SoftwareName
if (!$installLocation)  { Write-Warning "Can't find $packageName install location"; return }
Write-Host "$packageName installed to '$installLocation'"

I also noted on the Chocolatey package discussion, a few people have had issues over the years when the installer fails if doing a silent install and it wants to close some running programs. However, I super-doubt that's the case here (different error code, and what would be running??)

Anyway, since this repros on Windows Server Core without ue4-docker, then I'd suggest raising it to Chocolatey (not sure what their support channels are), and/or perhaps the Windows Containers issue tracker since this seems to be affected by the isolation mode, suggesting it's a container issue at its core.

---

To split the difference in the possible problems, try repeating Test 5, but run

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

before downloading and running the git installer manually in the same container instance. That will help identify if it's something about Chocolatey itself, or something about the git package specifically.

Another possible test you might want to try in the meantime, is using a DockerFile that starts from server core, and installs chocolatey and then the git package as two different RUN steps, rather than one RUN step like ue4-docker does, to emulate a system restart and clear any file-in-use issues.

[TomSmithGR]

Thanks for the help.

I have opened a ticket with chocolatey relating to this issue here:
chocolatey-community/chocolatey-packages#1776

On that issue I have built a dockerfile that installs chocolatey, then choco git as a separate RUN line. This errors out with process isolation, and installs otherwise.

Weirdly the git installer seems to produce some error text when run in a RUN statement from a dockerfile. It complains about the extra commas in /Components, and return 1. I see none of this when running the commands interactively. The error text is displayed on either isolation mode.
Dockerfile.txt

[slonopotamus]

Hmm... I wonder which part (Windows, Chocolatey, Git, Docker?) has changed. I successfully built ltsc2022 back in September when was working on #199. One major difference I see is that I was using Windows Server 2022 as a host instead of Windows 11, but this might be irrelevant. Maybe you could to try older Git versions?

[TomSmithGR]

I can probably rule out Git, I have tried every version since 2.31.1, and get the same result on each.
Windows host sounded like an interesting avenue, so I spun up a VM and see if I get the same problems with server 22 as host OS. The same docker file that fails with process isolation with win11 as host, succeeds with server 2022 as host.

This was done with the latest choco, and git releases. Interestingly the same git.install install location error is showing, but git does get installed correctly.

docker build output

PS C:\Users\testdocker\gittest> docker build --isolation=process .
Sending build context to Docker daemon  3.072kB
Step 1/5 : FROM mcr.microsoft.com/windows/servercore:ltsc2022
ltsc2022: Pulling from windows/servercore
8f616e6e9eec: Pull complete
4d1d74adc6a9: Pull complete
Digest: sha256:1f8965b9b4e2097ac78590ba652f069eafd5b6a0a4e9e603a415d362bfb7638c
Status: Downloaded newer image for mcr.microsoft.com/windows/servercore:ltsc2022
 ---> 136110e1a05c
Step 2/5 : SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'Continue'; $verbosePreference='Continue';"]
 ---> Running in 3d4652165df7
Removing intermediate container 3d4652165df7
 ---> dcc0da35f0c0
Step 3/5 : ENV CHOCO_URL=https://chocolatey.org/install.ps1
 ---> Running in 4e407a001325
Removing intermediate container 4e407a001325
 ---> fe48d8a5cf2a
Step 4/5 : RUN Set-ExecutionPolicy Bypass -Scope Process -Force;  [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]'Tls,Tls11,Tls12';  iex ((New-Object System.Net.WebClient).DownloadString("$env:CHOCO_URL"));
 ---> Running in 774f8ed5f97b
Forcing web requests to allow TLS v1.2 (Required for requests to Chocolatey.org)
Getting latest version of the Chocolatey package for download.
Not using proxy.
Getting Chocolatey from https://community.chocolatey.org/api/v2/package/chocolatey/0.11.3.
Downloading https://community.chocolatey.org/api/v2/package/chocolatey/0.11.3 to C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip
Not using proxy.
Extracting C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip to C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall
VERBOSE: Preparing to expand...
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\_re
ls\.rels'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\cho
colatey.nuspec'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateysetup.psm1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\init.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\VERIFICATION.txt'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\choco.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\choco.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\choco.exe.manifest'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\CREDITS.txt'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\LICENSE.txt'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\chocolateyInstaller.psm1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\chocolateyProfile.psm1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\chocolateyScriptRunner.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\ChocolateyTabExpansion.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Format-FileSize.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-CheckSumValid.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-ChocolateyUnzip.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-ChocolateyWebFile.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-EnvironmentVariable.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-EnvironmentVariableNames.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-FtpFile.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-OSArchitectureWidth.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-PackageParameters.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-ToolsLocation.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-UACEnabled.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-UninstallRegistryKey.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-VirusCheckValid.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-WebFile.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-WebFileName.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Get-WebHeaders.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-BinFile.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyDesktopLink.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyEnvironmentVariable.ps
1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyExplorerMenuItem.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyFileAssociation.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyInstallPackage.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyPackage.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyPath.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyPinnedTaskBarItem.ps1'
.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyPowershellCommand.ps1'
.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyShortcut.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyVsixPackage.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-ChocolateyZipPackage.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Install-Vsix.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Set-EnvironmentVariable.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Set-PowerShellExitCode.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Start-ChocolateyProcessAsAdmin.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Test-ProcessAdminRights.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Uninstall-BinFile.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Uninstall-ChocolateyEnvironmentVariable.
ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Uninstall-ChocolateyPackage.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\UnInstall-ChocolateyZipPackage.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Update-SessionEnvironment.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Write-ChocolateyFailure.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Write-ChocolateySuccess.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Write-FileUpdateLog.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\functions\Write-FunctionCallLogMessage.ps1'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\choco.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\choco.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\chocolatey.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\chocolatey.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cinst.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cinst.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\clist.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\clist.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cpack.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cpack.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cpush.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cpush.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cuninst.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cuninst.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cup.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cup.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cver.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\cver.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\redirects\RefreshEnv.cmd'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\7z.dll'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\7z.dll.manifest'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\7z.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\7z.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\7z.exe.manifest'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\7zip.license.txt'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\checksum.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\checksum.exe.config'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\checksum.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\checksum.license.txt'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\shimgen.exe'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\shimgen.exe.ignore'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\tools\shimgen.license.txt'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\[Co
ntent_Types].xml'.
VERBOSE: Created
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\pac
kage\services\metadata\core-properties\0f188391ebb44f408b3c77de8dcfdfe0.psmdcp'
.
Installing Chocolatey on the local machine
VERBOSE: Loading module from path
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateysetup.psm1'.
VERBOSE: Exporting function 'Initialize-Chocolatey'.
VERBOSE: Importing function 'Initialize-Chocolatey'.
VERBOSE: Loading module from path
'C:\Users\ContainerAdministrator\AppData\Local\Temp\chocolatey\chocoInstall\too
ls\chocolateyInstall\helpers\chocolateyInstaller.psm1'.
Creating ChocolateyInstall as an environment variable (targeting 'Machine')
  Setting ChocolateyInstall to 'C:\ProgramData\chocolatey'
WARNING: It's very likely you will need to close and reopen your shell
  before you can use choco.
Restricting write permissions to Administrators
We are setting up the Chocolatey package repository.
The packages themselves go to 'C:\ProgramData\chocolatey\lib'
  (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin'
  and points to an executable in 'C:\ProgramData\chocolatey\lib\yourPackageName'.

Creating Chocolatey folders if they do not already exist.

WARNING: You can safely ignore errors related to missing log files when
  upgrading from a version of Chocolatey less than 0.9.9.
  'Batch file could not be found' is also safe to ignore.
  'The system cannot find the file specified' - also safe.
chocolatey.nupkg file not installed in lib.
 Attempting to locate it from bootstrapper.
PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...
WARNING: Not setting tab completion: Profile file does not exist at
'C:\Users\ContainerAdministrator\Documents\WindowsPowerShell\Microsoft.PowerShe
ll_profile.ps1'.
Chocolatey (choco.exe) is now ready.
You can call choco from anywhere, command line or powershell by typing choco.
Run choco /? for a list of functions.
You may need to shut down and restart powershell and/or consoles
 first prior to using choco.
Ensuring Chocolatey commands are on the path
Ensuring chocolatey.nupkg is in the lib folder
Removing intermediate container 774f8ed5f97b
 ---> ef6c6af3e7fa
Step 5/5 : RUN choco install -y git --params "'/GitOnlyOnPath /NoAutoCrlf /WindowsTerminal /NoShellIntegration /NoCredentialManager'"
 ---> Running in e205047435fa
Chocolatey v0.11.3
Installing the following packages:
git
By installing, you accept licenses for the packages.
Progress: Downloading git.install 2.34.1... 100%
Progress: Downloading chocolatey-core.extension 1.3.5.1... 100%
Progress: Downloading git 2.34.1... 100%

chocolatey-core.extension v1.3.5.1 [Approved]
chocolatey-core.extension package files install completed. Performing other installation steps.
 Installed/updated chocolatey-core extensions.
 The install of chocolatey-core.extension was successful.
  Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-core'

git.install v2.34.1 [Approved]
git.install package files install completed. Performing other installation steps.
Parameter: no git shell integration
Using Git LFS
Installing 64-bit git.install...
git.install has been installed.
WARNING: Can't find git.install install location
  git.install can be automatically uninstalled.
Environment Vars (like PATH) have changed. Close/reopen your shell to
 see the changes (or in powershell/cmd.exe just type `refreshenv`).
 The install of git.install was successful.
  Software installed to 'C:\Program Files\Git\'

git v2.34.1 [Approved]
git package files install completed. Performing other installation steps.
 The install of git was successful.
  Software install location not explicitly set, it could be in package or
  default install location of installer.

Chocolatey installed 3/3 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Removing intermediate container e205047435fa
 ---> 25818678f9a2
Successfully built 25818678f9a2

[TomSmithGR]

I guess that leaves Host OS or Docker version changes as potential culprits for the behaviour (as server 2022 tests were using Microsoft docker distribution).

[slonopotamus]

So, we're trying to blame Windows 11 process isolation as the root cause of this issue?

[slonopotamus]

server 2022 tests were using Microsoft docker distribution

You can use Stevedore so you have 100% identical Docker engine on both client and server Windows.

[TomSmithGR]

Ok, I have repeated the test on server 2022 using Stevedore v0.0.2, the test passes, and git installs correctly.

I'm having some problems getting stevedore to install on win11, its erroring out creating a user, both through chocolatey and directly with the msi. I just loggged a bug report here: slonopotamus/stevedore#12.

[TBBle]

@TomSmithGR As a quick note, I would find it easier to read if you put the output text inside code-blocks (```-delimited blocks).

[TomSmithGR]

TBBIe: thanks for the tip, sorry a bit new to markdown, I will correct the posts.

Ok, I managed to get stevedore working, and repeated the tests. Git still fails on win11 with process isolation, even with the same docker version. It must be something different between windows 11 and server 2022 hosts when using process isolation.

Results of docker build on win11 using stevedore v0.0.2 and process isolation.
win11-stevedore.txt

[adamrehn]

Oh dear, I hope this isn't another ABI breakage issue like we saw back in February 2020, this time caused by some update to Windows 11. Microsoft made a point of promising full ABI compatibility between existing Windows Server 2022 container images and all future versions of Windows Server 2022 and Windows 11, ensuring process isolation mode never breaks.