none
Latest servercore image hanging on start RRS feed

  • Question

  • Hello,

    Have a problem that surfaced between yesterday around noon and midnight in one of our applications that leverages the servercore docker image. It appears that once the updated image was pulled we could no longer issue any 'RUN' commands. The container is created but any attempt to start/RUN fails with no error message (seems to just be hard locked). We're leveraging Team City to manage our builds and after an hour get:

    container <snip> encountered an error during Start: failure in a Windows system call: The wait operation timed out. (0x102)

    There were no changes on our side to prompt this. Rolling back to tag 10.0.17763.973 and we can start the container again. Was previously pointing at ltsc2019, also tried 1809. Running docker engine 19.03.05.

    Thursday, February 13, 2020 3:42 AM

Answers

  • This appears to be working again after the update released a couple hours ago.
    • Marked as answer by Ben Newton Thursday, February 13, 2020 11:45 AM
    Thursday, February 13, 2020 11:45 AM

All replies

  • This appears to be working again after the update released a couple hours ago.
    • Marked as answer by Ben Newton Thursday, February 13, 2020 11:45 AM
    Thursday, February 13, 2020 11:45 AM
  • Please see this post for addition context into the problem you were seeing.
    Thursday, February 13, 2020 11:47 PM
  • We have three Azure servers which run Windows Containers using the Docker API. After the latest set of Windows updates, the containers are no longer starting. Now that the matching ltsc2019 container got withdrawn by Microsoft, there appears to be no way to fix this issue. The link from Michael indicates we should keep the security update, but right now a system to help world health research has been killed with no way forward. If someone could point me at the definitive place where this is discussed or being looked into, or any sort of timeline for a fix, or how to work around it in the meantime, there is a team here very much looking forward to knowing. Thanks.
    Friday, February 14, 2020 8:58 AM
  • It sounds like your host machines weren't patched with the Feb updates since it sounds like you encountered the problem.  If that is indeed the case you should be able to simply re-pull the ltsc2019 tag which was reverted to the January image and everything will work.  If this is not the case, then I think I would need more details?  What updates are on your host machine and what is the digest and tag of the image you are using?
    Friday, February 14, 2020 3:18 PM