none
Using the latest base OS images and updating docker RRS feed

  • General discussion

  • Hello,

    We have recently uploaded to Docker Hub these new base OS images:

    • microsoft/nanoserver:10.0.14393.321 
    • microsoft/windowsservercore:10.0.14393.321

    These images correspond to the latest update of Windows Server 2016, and are now the "latest" tags for their respective repositories.

    Important: In order to use these images, you will need to use the latest CS version of the Docker Engine and the Docker client. You can get these here: https://download.docker.com/components/engine/windows-server/cs-1.12/docker-1.12.2.zip

    If you try to pull these images with an older version of docker, you will see this error:
    "failed to register layer: re-exec error: exit status 1: output: hard links not supported with legacy writer"

     



    Wednesday, October 12, 2016 6:51 PM
    Moderator

All replies

  • Docker 1.12 is broken and you need 1.13 version of Docker to make docker engine work properly on Windows 10 as documented here https://github.com/docker/for-win/issues/131 
    Thursday, October 13, 2016 2:17 AM
  • same error here with Server:
     Version:      1.13.0-dev

    (btw: would be nice if you can provide clickable links) :)

    • Edited by rs38 Friday, October 14, 2016 5:28 PM
    Friday, October 14, 2016 5:26 PM
  • The documentation and version numbers are pretty confusing here!

    To make things (hopefully) a bit clearer:

    Pulling these images with Docker engine 1.13.0-dev (which is still linked on the Windows 10 Quickstart page!) fails as described above:
    C:\Users\andreas>docker version
    Client:
     Version:      1.13.0-dev
     API version:  1.25
     Go version:   go1.7.1
     Git commit:   762556c
     Built:        Sat Oct  1 11:16:14 2016
     OS/Arch:      windows/amd64
    
    Server:
     Version:      1.13.0-dev
     API version:  1.25
     Go version:   go1.7.1
     Git commit:   762556c
     Built:        Sat Oct  1 11:16:14 2016
     OS/Arch:      windows/amd64
    
    C:\Users\andreas>docker pull microsoft/windowsservercore:10.0.14393.321
    10.0.14393.321: Pulling from microsoft/windowsservercore
    9c7f9c7d9bc2: Already exists
    de5064718b3f: Extracting [==================================================>] 613.1 MB/613.1 MB
    failed to register layer: re-exec error: exit status 1: output: hard links not supported with legacy writer
    
    C:\Users\andreas>

    But pulling these images with Docker engine 1.12.2 (linked above) succeeds:

    C:\Users\andreas>docker version
    Client:
     Version:      1.12.2-cs2-ws-beta
     API version:  1.25
     Go version:   go1.7.1
     Git commit:   050b611
     Built:        Tue Oct 11 02:35:40 2016
     OS/Arch:      windows/amd64
    
    Server:
     Version:      1.12.2-cs2-ws-beta
     API version:  1.25
     Go version:   go1.7.1
     Git commit:   050b611
     Built:        Tue Oct 11 02:35:40 2016
     OS/Arch:      windows/amd64
    
    C:\Users\andreas>docker pull microsoft/windowsservercore:10.0.14393.321
    10.0.14393.321: Pulling from microsoft/windowsservercore
    
    9c7f9c7d9bc2: Already exists
    de5064718b3f: Pull complete
    Digest: sha256:fe34ea447bf1c3db743813d64189c0949bf96015a74632033bfb275e12a6fa7c
    Status: Downloaded newer image for microsoft/windowsservercore:10.0.14393.321
    
    C:\Users\andreas>

    @Ender:
    Could you please also update the download link on the Windows 10 Quickstart page ?
    Also see Issue 402
    Saturday, October 15, 2016 6:19 PM
  • Hi Andreas,

    I tried "docker pull microsoft/nanoserver" using 1.12.2, api version 1.25.

    

    That didn't work for me. However, running with docker 1.13. 0 did the trick.


    Saturday, October 15, 2016 9:07 PM
  • Ok, I just noticed a misunderstanding on my side:

    The download link to version 1.13.0-dev on the Windows 10 Quickstart page is pointing to a continuous integration build that is updated with each commit on Github.

    So referring to version numbers does not really help here. What matters is the git commit hash (and for convenience the build date).

    The version 1.13.0-dev which failed for me was from commit 762556c on Oct 1.
    The version 1.12.2 linked above seems to be from commit 050b611 on Oct 11.

    Obviously, there was some commit in between those which fixed the error mentioned above.

    @Hamid:
    Your version 1.12.2 is from commit 62d9ff9 on Sep 23, so the fix was not in there yet, I suppose. But your version 1.13.0-dev is from commit 2a3ba03 on Oct 15, that's why that one worked for you.

    Monday, October 17, 2016 10:00 AM
  • Today I found new 1.13.0-dev binary (built Oct 29) in  https://master.dockerproject.org/

    1.13.0-dev (Built Oct 7, go1.7.1) on Windows 10, I could not start hyper-v container (freeze dockerd)

    1.13.0-dev (Built Oct 29, go1.7.3) on Windows 10, I can run hyper-v container fine.

    Sunday, October 30, 2016 11:57 PM