Docker Community Forums

Share and learn in the Docker community.

Syscall did not complete within operation timeout. This may indicate a platform issue

Hi,
looking for help to track down the configuration issue that may prevent the container from running.
I have tested on a Win2016 server the container, it works very good. It si just on an enterprise win2016 server that may security configs that are affecting
help is much appreciated

Expected behavior

Hello world image to run and display message

Actual behavior

time=“2019-12-03T11:20:51.604089500-05:00” level=info msg=“goroutine stacks written to E:\DockerData\goroutine-stacks-
2019-12-03T112051-0500.log”
time=“2019-12-03T11:21:52.505630600-05:00” level=warning msg=“Syscall did not complete within operation timeout. This may indicate a platform issue. If it a
ppears to be making no forward progress, obtain the stacks and see if there is a syscall stuck in the platform API for a significant length of time.” cid=53
3782c9ca847081aa68526386575cc195dd5fa94bead26defcef3b5cec19d58 timeout=4m0s

Information

PS E:> docker version
Client: Docker Engine - Enterprise
Version: 19.03.3
API version: 1.40
Go version: go1.12.10
Git commit: cde21d3829
Built: 10/08/2019 17:59:26
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Enterprise
Engine:
Version: 19.03.3
API version: 1.40 (minimum version 1.24)
Go version: go1.12.10
Git commit: cde21d3829
Built: 10/08/2019 17:57:54
OS/Arch: windows/amd64
Experimental: false