hcsshim: encountered an error during hcsshim::System::waitBackground: failure in in windows container mode. on fast ring and latest 1909 release.

Description

encountered an error during hcsshim::System::waitBackground: failure in in windows container mode. on fast ring and latest 1909 release.

Steps to reproduce the issue:

docker run -it mcr.microsoft.com/powershell:lts-alpine-3.10

Describe the results you received:

PS /> exit
time="2020-04-22T09:58:24+02:00" level=error msg="Error waiting for container: failed to shutdown container: container
69fc778d98e49bc2cd3f6e54612ff27bb7663cbe891b2a152d707f9620e4d08a encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110): subsequent terminate failed container 69fc778d98e49bc2cd3f6e54612ff27bb7663cbe891b2a152d707f9620e4d08a encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110)"
PS C:\Users\bartp>

Client: Docker Engine - Community Version: 19.03.8 API version: 1.40 Go version: go1.12.17 Git commit: afacb8b Built: Wed Mar 11 01:23:10 2020 OS/Arch: windows/amd64 Experimental: true

docker version

Server: Docker Engine - Community Engine: Version: 19.03.8 API version: 1.40 (minimum version 1.24) Go version: go1.12.17 Git commit: afacb8b Built: Wed Mar 11 01:37:20 2020 OS/Arch: windows/amd64 Experimental: true

docker info

Client: Debug Mode: false Plugins: app: Docker Application (Docker Inc., v0.8.0) buildx: Build with BuildKit (Docker Inc., v0.3.1-tp-docker) mutagen: Synchronize files with Docker Desktop (Docker Inc., testing)

Server: Containers: 6 Running: 1 Paused: 0 Stopped: 5 Images: 359 Server Version: 19.03.8 Storage Driver: windowsfilter (windows) lcow (linux) Windows: LCOW: Logging Driver: json-file Plugins: Volume: local Network: ics internal l2bridge l2tunnel nat null overlay private transparent Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog Swarm: inactive Default Isolation: hyperv Kernel Version: 10.0 19608 (19608.1000.amd64fre.rs_prerelease.200410-1438) Operating System: Windows 10 Pro Version 2004 (OS Build 19608.1006) OSType: windows Architecture: x86_64 CPUs: 4 Total Memory: 31.88GiB Name: PCI ID: KUM5:H6SV:J3EE:5FI3:Q5PL:TA2W:ZRIS:CNBG:52AF:EL3B:F7DB:H6SG Docker Root Dir: C:\ProgramData\Docker Debug Mode: true File Descriptors: -1 Goroutines: 35 System Time: 2020-04-22T10:03:27.9886332+02:00 EventsListeners: 1 Registry: https://index.docker.io/v1/ Labels: Experimental: true Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine

PS /> exit time=“2020-04-22T10:13:36+02:00” level=error msg=“Error waiting for container: failed to shutdown container: container 55b3e99dc6bfda03d6e0be4ec000f5c6c3ee29e8d973389b0d3f1dbaea6cdaf4 encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110): subsequent terminate failed container 55b3e99dc6bfda03d6e0be4ec000f5c6c3ee29e8d973389b0d3f1dbaea6cdaf4 encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110)”

docker version Client: Docker Engine - Community Version: 19.03.8 API version: 1.40 Go version: go1.12.17 Git commit: afacb8b Built: Wed Mar 11 01:23:10 2020 OS/Arch: windows/amd64 Experimental: true

docker info Client: Debug Mode: false Plugins: app: Docker Application (Docker Inc., v0.8.0) buildx: Build with BuildKit (Docker Inc., v0.3.1-tp-docker)

Server: Containers: 7 Running: 1 Paused: 0 Stopped: 6 Images: 377 Server Version: 19.03.8 Storage Driver: windowsfilter (windows) lcow (linux) Windows: LCOW: Logging Driver: json-file Plugins: Volume: local Network: ics internal l2bridge l2tunnel nat null overlay private transparent Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog Swarm: inactive Default Isolation: hyperv Kernel Version: 10.0 18363 (18362.1.amd64fre.19h1_release.190318-1202) Operating System: Windows 10 Enterprise Version 1909 (OS Build 18363.752) OSType: windows Architecture: x86_64 CPUs: 12 Total Memory: 31.81GiB Name: LT-BAP-T-NL ID: AVXB:O6GT:DLC7:DZXN:OF46:3QIY:GANI:BMDV:R2TY:LN27:ZH44:YZ6X Docker Root Dir: C:\ProgramData\Docker Debug Mode: true File Descriptors: -1 Goroutines: 49 System Time: 2020-04-22T10:13:53.2893047+02:00 EventsListeners: 1 Registry: https://index.docker.io/v1/ Labels: Experimental: true Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine

cc: @StefanScherer , @simonferquel

About this issue

Original URL
State: open
Created 4 years ago
Reactions: 20
Comments: 46

Links to this issue

python - Docker build failed on Windows 10 Pro x64 - Stack Overflow

Most upvoted comments

They broke it with version 2.2.0.4. Uninstalling Docker Desktop and installing version 2.2.0.3 resolved the issue. Noticed that they added a “Known issue” to the release notes for 2.2.0.4 saying: “Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the experimental WSL backend.”

Funny way of saying we broke the most fundamental thing of LCOW, please use a virtual machine instead.

+19

AbsurdusAdeptus on Apr 30, 2020

Sad part is that this was working just 2 0.0.0.x versions ago. Completely breaking a feature as important as LCOW (even an experimental one) and putting a small aside in the release notes as “some cli commands fail” is pretty ridiculous.

AbsurdusAdeptus on Apr 30, 2020

Also happens on dockerEE which version greater than 19.03.5

so it could be fixed by force downgrading the dockerEE version on Server 2019

Install-Package -Name docker -ProviderName DockerMsftProvider -Force -RequiredVersion 19.03.5

Kagamia on Aug 28, 2021

I have same error on windows. It happens always when dockerfile uses “RUN” command.

AC740 on Aug 30, 2020

The command ‘/bin/sh -c apk add --update redis’ returned a non-zero code: 4294967295: failed to shutdown container: container a0ec71fb66524cdd30fd9e3ff1501afa288ba6c51bea2255976faaad9889f6f0 encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110): subsequent terminate failed container a0ec71fb66524cdd30fd9e3ff1501afa288ba6c51bea2255976faaad9889f6f0 encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110)

i am having this error anyone can solve this ?

Ayush1026 on Aug 5, 2020

I can reproduce as well, running

Windows: 19608.1006 Docker Desktop: 2.3.0.0 (44472) Docker Engine: 19.03.8

robearlam on Apr 22, 2020

I can reproduce on same versions. Seems to be a LCOW only issue. Works fine when engine is Linux (with WSL2 backend)

pbering on Apr 22, 2020

Issue is present on server 2019 insider version 2004 build 20236.1000

Tested Docker 2.4.0.0 and Docker 2.4.1.0

Step 3/6 : RUN yum install -y epel-release
 ---> Running in b06e80476769
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors
 * base: centos.mirror.fr.planethoster.net
 * extras: centos.mirror.fr.planethoster.net
 * updates: centos.mirror.fr.planethoster.net
Resolving Dependencies
--> Running transaction check
---> Package epel-release.noarch 0:7-11 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package                Arch             Version         Repository        Size
================================================================================
Installing:
 epel-release           noarch           7-11            extras            15 k

Transaction Summary
================================================================================
Install  1 Package

Total download size: 15 k
Installed size: 24 k
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : epel-release-7-11.noarch                                     1/1
  Verifying  : epel-release-7-11.noarch                                     1/1

Installed:
  epel-release.noarch 0:7-11

Complete!
The command '/bin/sh -c yum install -y epel-release' returned a non-zero code: 4294967295: failed to shutdown container: container b06e8047676935a1dc2944e5152a909f75526ae69f708e48e1403d72fbce2cc7 encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110): subsequent terminate failed container b06e8047676935a1dc2944e5152a909f75526ae69f708e48e1403d72fbce2cc7 encountered an error during hcsshim::System::waitBackground: failure in a Windows system call: The virtual machine or container with the specified identifier is not running. (0xc0370110)```

This is still a problem in mcr.microsoft.com/windows/servercore/insider:10.0.20348.1

datduyng on Mar 24, 2022

It happen with WCOW and LCOW. For linux, of course there is alternative like WSL2 or Hyper-V. But with Windows, there is no alternative.

philcar on Sep 28, 2020

They broke it with version 2.2.0.4. Uninstalling Docker Desktop and installing version 2.2.0.3 resolved the issue. Noticed that they added a “Known issue” to the release notes for 2.2.0.4 saying: “Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the experimental WSL backend.”

Funny way of saying we broke the most fundamental thing of LCOW, please use a virtual machine instead.

LCOW is great but lingering at the moment. I did create a roadmap ticket because many people are using LCOW at the moment. https://github.com/docker/roadmap/issues/79

bplasmeijer on Apr 30, 2020

I just blindly accepted an update to Docker Desktop – apparently I shouldn’t have done that. Seeing the same issue.

encountered an error during hcsshim::System::Start: failure in a Windows system call: The virtual machine or container exited unexpectedly. (0xc0370106)

lordscarlet on Mar 9, 2021

Does not work for me on the latest Docker 2.4.0.0 and 2004 with WSL2

michaelbaranov on Oct 29, 2020

The same happen with Windows containers, not only with LCOW. It work most of the time but sometime, a docker run fail with this message.

philcar on Sep 25, 2020

I see have the same on the stable channel Docker Desktop 2.2.0.5

michaelbaranov on Apr 22, 2020

Same for me on 1909 Docker Desktop : 2.2.0.5 Docker Engine: 19.03.8

jeanfrancoislarente on Apr 22, 2020