moby: LCOW: intermittent failures with "returned a non-zero code: 4294967295"

Using LCOW I occasionally see error messages like this

The command '/bin/sh -c dd if=/dev/urandom of=file1 bs=8 count=1' returned a non-zero code: 4294967295: failed to shutdown container: container de3925f530ce9fa61618d52c626dcf49746d8f0226454c5612183b080121dc05 encountered an error during WaitTimeout: failure in a Windows system call: winapi error #4294967295 (0xffffffff)

This particular case is with a simple Dockerfile:

FROM alpine:3.7
RUN dd if=/dev/urandom of=file1 bs=8 count=1

but the error happens intermittently, ie it works when run again. I’ve seen this error with several different Dockerfile so it’s likely independent of a specific file

I believe @jhowardmsft is aware of this issue so just filing it for the records.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 27 (8 by maintainers)

Most upvoted comments

This seems consistant now across windows 10 installations. The simplest build with a RUN failes with the same error:

FROM ubuntu
RUN echo bob

C:\test>docker build .
Sending build context to Docker daemon  982.8MB
Step 1/2 : FROM ubuntu
 ---> 7698f282e524
Step 2/2 : RUN echo bob
 ---> Running in 487eaca0dc74
bob
The command '/bin/sh -c echo bob' returned a non-zero code: 4294967295: failed to shutdown container: container 487eaca0dc744b4536deea54f8b7ff1fbd8a172fe39f7810a883f6a23f1b992f 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 487eaca0dc744b4536deea54f8b7ff1fbd8a172fe39f7810a883f6a23f1b992f 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)

AbsurdusAdeptus on Apr 30, 2020

Actually, even if I take out all of the commands from the dockerfile, it happens when running the image too

necroTaxonomist on Aug 2, 2018

so apparently this is still a thing. how are we supposed to use this thing?

4c74356b41 on Jun 24, 2018

nevermind, it actually just happens on any RUN commands

necroTaxonomist on Aug 2, 2018

Any updates on this? It is very flaky/intermittent for me… Getting the following error on Windows Docker Engine:19.03.5 Version: 2.2.0.3(42716) stable:

returned a non-zero code: 4294967295

gituser2291 on Feb 13, 2020

I have been running into the same problem while trying to build from a Dockerfile too.

Docker version:

Client:
 Version:      17.10.0-ee-preview-3
 API version:  1.33
 Go version:   go1.8.4
 Git commit:   1649af8
 Built:        Fri Oct  6 17:52:28 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.10.0-ee-preview-3
 API version:  1.34 (minimum version 1.24)
 Go version:   go1.8.4
 Git commit:   b8571fd
 Built:        Fri Oct  6 18:01:48 2017
 OS/Arch:      windows/amd64
 Experimental: true

Windows version:

Edition:  Windows Server 2019 Standard
Version: 1809
OS build: 17763.379

Are there any updates on this?

terryxychan on Sep 20, 2019