Forum Discussion

David Hirschfeld's avatar
David Hirschfeld
Copper Contributor
Jul 30, 2017

Old containers don't work on Windows Server Insiders?

Trying to run a windowsservercore container built on a Windows Server standard build gives me an error:

 

docker : C:\docker\docker.exe: Error response from daemon: container d87c04be7972d3e5870ed1aa79e5b5c569764e4ada89cc6246d55b2f0bb8425d encountered an error during 
CreateContainer: failure in a Windows system call: The operating system of the container does not match the operating system of the host.

 

Is it true that you can't run any containers unless they were built on Windows Server Insiders?

 

PS C:\> docker version
Client:
 Version:      17.06.0-dev
 API version:  1.31
 Go version:   go1.8.3
 Git commit:   286216d
 Built:        Sat Jul 29 00:03:50 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.06.0-dev
 API version:  1.31 (minimum version 1.24)
 Go version:   go1.8.3
 Git commit:   b6d164e
 Built:        Sat Jul 29 00:27:13 2017
 OS/Arch:      windows/amd64
 Experimental: false

 

  • Patrick Lang's avatar
    Patrick Lang
    Aug 11, 2017

    `docker run --isolation=hyperv microsoft/windowsservercore` will work on Windows Server Insider & Windows 10 Insider builds. Because the kernel is different between the shipped Windows Server 2016 OS - we need to use Hyper-V isolation. That will run that container with the same kernel so there aren't any incompatibilities.

     

    Can you give that a try and let us know how it works?

     

    Thanks!
    Patrick

  • I'm trying containers feature on windows server insider like you, and YES old containers based on windows server does not work anymore, you have to install same container host and container version. So, for example if you want to run Nano Server lastest version, you have to run Nano Server insider version.
    docker pull microsoft/nanoserver-insider
    or version powershell: docker pull microsoft/nanoserver-insider
    I'm find so many issues with that, but we can help and report them.
    Hope it helps.
    • David Hirschfeld's avatar
      David Hirschfeld
      Copper Contributor

      Not exactly a smooth upgrade path - rebuild everything from scratch?!

       

      What happens when the current insider version gets released ot the stable channel? Will the containers we build on insiders not work there as well?? It seems to make the whole insiders idea pointless for me - I can't afford the time to rebuild everything 3 times over.

       

      Before I pack it all in and revert to the stable build would anyone from MS care to let me know if it's planned for insiders to *ever* be able to run containers built on the Standard Windows Server 2016?

      • Patrick Lang's avatar
        Patrick Lang
        Icon for Microsoft rankMicrosoft

        `docker run --isolation=hyperv microsoft/windowsservercore` will work on Windows Server Insider & Windows 10 Insider builds. Because the kernel is different between the shipped Windows Server 2016 OS - we need to use Hyper-V isolation. That will run that container with the same kernel so there aren't any incompatibilities.

         

        Can you give that a try and let us know how it works?

         

        Thanks!
        Patrick

  • Hi, am new in the community, I would to learn more about windows Server X, please someone can tell how and where to start. waiting for your reply bernardocangulo@hotmail.com

Resources