none
I tried to run docker using a WinServer 2016 TP4 core/nano container image on a WinServer 2016 TP4 GUI container host RRS feed

  • Question

  • Hi all,

    I have gone through the following steps and finally reached an error which I think it stonewalled my attempt to run docker using a different container image than the container host. I realized it being work in progress: https://msdn.microsoft.com/en-us/virtualization/windowscontainers/about/work_in_progress

    1. Enable Hyper-V on the host.
    2. Download TP4 ISO and install it using Hyper-V.
    3. Enable the Containers feature within the newly deployed TP4.
    4. Download from  https://aka.ms/tp4/docker and deploy docker to system32 folder.
    5. Run docker daemon.
    6. Get container base images using the following commands:
    7. Install-PackageProvider ContainerProvider –Force
    8. Install-ContainerImage -Name NanoServer -Version 10.0.10586.0
    9. Install-ContainerImage -Name WindowsServerCore -Version 10.0.10586.0
    10. Tag the container images as latest
    11. Create the Virtual Switch: New-VMSwitch –name “Virtual Switch”
    12. Docker run –name newserver–it nanoserver cmd
    13. Got the error about different container/host OS image version.

    The error message was: Win32 API call returned error r1=322480209 err=The operating system of the container does not match the operating system of the host.

    Is this going to be be fixed in the final release and will it allow require the same OS versions between the container and the host OS image?

    Thanks,

    Dickson




    • Edited by Dickson.Lam Tuesday, February 16, 2016 5:06 PM
    Tuesday, February 16, 2016 4:10 PM

Answers

  • You can run a container with a nano server base OS, on a different host OS, when starting it as a Hyper-V container.

    Configure Host for Hyper-V:

    https://msdn.microsoft.com/en-us/virtualization/windowscontainers/deployment/deployment .

    Hyper-V Containers:

    https://msdn.microsoft.com/en-us/virtualization/windowscontainers/management/hyperv_container .

    I do not have an answer on future compatibility.

    neilp

    Tuesday, February 16, 2016 5:55 PM