none
Can't run a container on Windows Server 2016 TP5: winapi error 0xc000070a RRS feed

  • Question

  • Hi,

    I had a VM with Windows Server 2016 TP5 (b14300) with installer Containers feature and it worked fine.

    Unfortunately I lost this VM, then repeated all steps to install OS and docker, but when I try to run a container, I get this:

    c:\>docker run -d -p 80:80 microsoft/iis:windowsservercore ping -t localhost
    7ab2f593703e8b134fc99e680cc90b44c26747d4d3aedc430063ed4167766579
    docker: Error response from daemon: container 7ab2f593703e8b134fc99e680cc90b44c26747d4d3aedc430063ed4167766579 encountered an error during Start failed in Win32: winapi error #3221227274 (0xc000070a).

    There is also an error in windows logs:

    Failed to start compute system: container 563f9ecf4bc5795f6b9cf7d924a78b45dc7be43c45871d20ef291de4941c6631 encountered an error during Start failed in Win32: winapi error #3221227274 (0xc000070a)

    I tried with 1.12.0-dev, 1.12.0 versions, no success.

    Thanks.

    Tuesday, August 2, 2016 5:54 PM

Answers

  • workaround:

    1. Change date to 25 July 2016
    2. run any container (docker run -it windowsservercore:10.0.14300.1000 cmd)
    3. exit from container
    4. change date back
    5. any container works fine until reboot

    if you have domain and time-autosynchronization then use next powershell command in separate powershell console:
    for(;;){sleep 1;Set-Date -Date "2016-07-25" }


    Wednesday, August 3, 2016 8:49 AM
  • We have now root caused this issue.  Please see:

    https://social.msdn.microsoft.com/Forums/sharepoint/en-US/dfa9ce56-d9c1-408a-82e0-bec38d71a286/update-for-windows-container-base-os-images-base-os-images-now-in-docker-hub?forum=windowscontainers

    Thank you!


    -Taylor

    Friday, August 5, 2016 8:46 PM

All replies

  • I'm having the same issue on the same version; see here. Does your error message include stuff about the filter storage driver failing to remove the root filesystem?
    Tuesday, August 2, 2016 6:08 PM
  • Also getting this error! Seemed to start yesterday. 
    Tuesday, August 2, 2016 6:16 PM
  • Yep, I have similar error when I try to remove a failed container. 
    Tuesday, August 2, 2016 6:30 PM
  • yes, i got the same error, but a week ago, it succeeded with the same command.
    Wednesday, August 3, 2016 2:12 AM
  • workaround:

    1. Change date to 25 July 2016
    2. run any container (docker run -it windowsservercore:10.0.14300.1000 cmd)
    3. exit from container
    4. change date back
    5. any container works fine until reboot

    if you have domain and time-autosynchronization then use next powershell command in separate powershell console:
    for(;;){sleep 1;Set-Date -Date "2016-07-25" }


    Wednesday, August 3, 2016 8:49 AM
  • workaround:

    1. Change date to 25 July 2016
    2. run any container (docker run -it windowsservercore:10.0.14300.1000 cmd)
    3. exit from container
    4. change date back
    5. any container works fine until reboot

    if you have domain and time-autosynchronization then use next powershell command in separate powershell console:
    for(;;){sleep 1;Set-Date -Date "2016-07-25" }


    It works... Thank you... But.. Why?!
    Wednesday, August 3, 2016 9:11 AM
  • Can confirm, works for me too. I also wonder why?
    Wednesday, August 3, 2016 2:17 PM
  • Would also like explanation of why this works, and what is being done to actually fix the problem instead of provide a silly work-around like this.

    Wednesday, August 3, 2016 4:43 PM
  • I don't know why this works :) Maybe time-bomb?

    On github already exists links to new docker 1.13 and new image version 10.0.14300.1030 they are works.

    https://github.com/docker/docker/issues/25336#issuecomment-237351168



    nigo


    Wednesday, August 3, 2016 8:48 PM
  • Hello,

    The reason for this workaround is due to a certificate expiring in TP5. We are currently working on updating the images up on Git Hub as quickly as possible to use a version of the base image that does not run into this problem. Thank you for your patience.

    Regards,

    Ender

    Thursday, August 4, 2016 8:40 PM
    Moderator
  • We have now root caused this issue.  Please see:

    https://social.msdn.microsoft.com/Forums/sharepoint/en-US/dfa9ce56-d9c1-408a-82e0-bec38d71a286/update-for-windows-container-base-os-images-base-os-images-now-in-docker-hub?forum=windowscontainers

    Thank you!


    -Taylor

    Friday, August 5, 2016 8:46 PM