Docker containers failed to start after Window update KB5021235

[ntrappe-msft]

Important

Migrating Discussions to Issues. All customer inquiries should be in Issues.

Discussed in https://github.com/microsoft/Windows-Containers/discussions/329

^{Originally posted by senprabu March 5, 2023}
We are on Windows 2016 Server, running docker 19.03.11. We are using Docker EE. Last Dec 2022, we applied the cumulative Update for Windows Server 2016 KB5021235 (x64). After which our containers failed to start. The docker service is running, however the container don't start even after the command.

We have the following errors in Event Viewer:

General: failed to start container [module=libcontainerd namespace=moby error=container e361190d2840XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX encountered an error during hcsshim::System::Start: context deadline exceeded]

General: failed to cleanup after a failed Start [module=libcontainerd namespace=moby error=container d583cbd35d24XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX encountered an error during hcsshim::System::Terminate: context deadline exceeded]

General: Syscall did not complete within operation timeout. This may indicate a platform issue. If it appears 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. [timeout=4m0s traceID=3d38fXXXXXXXXXXXXXXXXXXXXXXXXXXXX spanID=bf10f8aee90XXXXXXXXXXXXXXXXXXXXX]

Any hekp would be appreciated.

[github-actions]

Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.

[winkingturtle-vmw]

@ntrappe-msft we are unable to see the discussions about this issue. One of the other new KB5046615 updates has broken our workflow and we are now unable to update to latest patch.

[ntrappe-msft]

@winkingturtle-vmw Hey, sorry about that. We've deleted the Discussion section for this GitHub so those discussions won't be available anymore. But, this Issue copied over the initial request from the user and it didn't have any additional comments.