I am working with custom Gitlab CI runners which use Docker Windows containers for testing.
All hosts use Windows 11 with Docker Desktop installed.
These hosts launch several hundred containers per day with multiple base images, each comprising ~25 GB with ~40 layers. Base image is always mcr.microsoft.com/windows:ltsc2019 .
Months of logging and thousands of container launches revealed that ~5% of all container launches fail randomly.
docker run shows no error message and just exits with error code -1.
If I create a file within the container (volume), it is not executed, so it will probably never be started.
The only error messages that are displayed can be found in the Windows log:
non-zero last wait result [traceID=18f027ad612cb05269dad2b39516c179 spanID=71697c6fdfdb4195 wait-result=-1070137082]
failed to shutdown container, and subsequent terminate also failed [namespace=moby error=container fa09bb2b554f0b9998d18e563bd133d6b27f91b1e23985ffa90643f6ccc4ef63 encountered an error during hcs::System::waitBackground: failure in a Windows system call: The connection with the virtual machine or container was closed. (0xc037010a) container=fa09bb2b554f0b9998d18e563bd133d6b27f91b1e23985ffa90643f6ccc4ef63 module=libcontainerd]
Description
I am working with custom Gitlab CI runners which use Docker Windows containers for testing. All hosts use Windows 11 with Docker Desktop installed. These hosts launch several hundred containers per day with multiple base images, each comprising ~25 GB with ~40 layers. Base image is always mcr.microsoft.com/windows:ltsc2019 .
Months of logging and thousands of container launches revealed that ~5% of all container launches fail randomly.
docker run shows no error message and just exits with error code -1.
If I create a file within the container (volume), it is not executed, so it will probably never be started.
The only error messages that are displayed can be found in the Windows log:
sending event [container=fa09bb2b554f0b9998d18e563bd133d6b27f91b1e23985ffa90643f6ccc4ef63 event=start event-info={fa09bb2b554f0b9998d18e563bd133d6b27f91b1e23985ffa90643f6ccc4ef63 fa09bb2b554f0b9998d18e563bd133d6b27f91b1e23985ffa90643f6ccc4ef63 2112 0 0001-01-01 00:00:00 +0000 UTC <nil>} module=libcontainerd namespace=moby]
non-zero last wait result [traceID=18f027ad612cb05269dad2b39516c179 spanID=71697c6fdfdb4195 wait-result=-1070137082]
failed to shutdown container, and subsequent terminate also failed [namespace=moby error=container fa09bb2b554f0b9998d18e563bd133d6b27f91b1e23985ffa90643f6ccc4ef63 encountered an error during hcs::System::waitBackground: failure in a Windows system call: The connection with the virtual machine or container was closed. (0xc037010a) container=fa09bb2b554f0b9998d18e563bd133d6b27f91b1e23985ffa90643f6ccc4ef63 module=libcontainerd]
Reproduce
docker run
Expected behavior
docker run should not exit with -1
docker version
docker info
Diagnostics ID
0
Additional Info
No response