none
1803 Images - The operating system of the container does not match the operating system of the host RRS feed

  • Question

  • I am trying to deploy a Server 2016 docker image to an ACS Engine Kubernetes cluster and am receiving this error:

    The operating system of the container does not match the operating system of the host


    To be clear, I am aware of the requirement for host and image to use the same version and I have verified that the node that this is being deployed to is running 1803 as well, so it should not have a mismatch, they should both be running 1803. Any ideas why I am seeing this issue?


    Sam Cogan Microsoft Azure MVP
    Blog | Twitter

    Tuesday, May 15, 2018 10:52 AM

Answers

All replies

  • Do you have access to actual underlying host to verify that it's in fact can not pull/run 1803 messages?
    Tuesday, May 15, 2018 1:23 PM
  • I have just tested running the exact same image on the host using docker run, and it runs fine. So it seems like this is something going wrong Kubernetes side. This is the full error I get in Kubernetes:

    Failed create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "olfactory-olm-app-deployment-64ddfc96dd-f6z5w": Error response from daemon: container 7929bfd27250d5465496de2bb6a37c5e41d492488ca7c8362a07637b464b5e52 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. (0xc0370101) extra info: {
        "SystemType": "Container",
        "Name": "7929bfd27250d5465496de2bb6a37c5e41d492488ca7c8362a07637b464b5e52",
        "Owner": "docker",
        "IsDummy": false,
        "VolumePath": "\\\\?\\Volume{0627cd58-20df-47a3-b494-8dd78e411995}",
        "IgnoreFlushesDuringBoot": true,
        "LayerFolderPath": "C:\\ProgramData\\docker\\windowsfilter\\7929bfd27250d5465496de2bb6a37c5e41d492488ca7c8362a07637b464b5e52",
        "Layers": [
            {
                "ID": "3a583df7-2f46-56a7-a452-7fc8abb7b534",
                "Path": "C:\\ProgramData\\docker\\windowsfilter\\89a92a6e8407219580d271d1689c7e479d26aa844ea92d60d9a0720eca6ab1a8"
            },
            {
                "ID": "2a988c67-9abf-5a34-85e1-0cfe5003064c",
                "Path": "C:\\ProgramData\\docker\\windowsfilter\\1a7a90531dbe455a4098d38b38793f0fd8b7f165ed8eae1f009492ef80aa3734"
            },
            {
                "ID": "6e5c7c2a-f3c3-5fd9-8040-bb2eeb5b6a9e",
                "Path": "C:\\ProgramData\\docker\\windowsfilter\\4ecd332ef1f0b0a519c8c1d640b42759919fe3d175e03f9e9ce490f482c87364"
            }
        ],
        "ProcessorWeight": 2,
        "HostName": "olfactory-olm-app-deployment-64ddfc96dd-f6z5w",
        "MappedDirectories": [],
        "HvPartition": false,
        "EnappintList": null,
        "Servicing": false,
        "AllowUnqualifiedDNSQuery": false
    }



    Sam Cogan Microsoft Azure MVP
    Blog | Twitter

    Tuesday, May 15, 2018 4:15 PM
  • So you logged on to the actual worker node inside your kubernetes cluster and those images worked fine there or you did it on different 1803 which is not worker node?

    Tuesday, May 15, 2018 4:54 PM
  • I logged onto the same worker node in the Kubernetes cluster and the image worked fine when using Docker Run.


    Sam Cogan Microsoft Azure MVP
    Blog | Twitter

    Tuesday, May 15, 2018 4:55 PM
  • OK, yes probably something on Kubernetes itself. Bearing in mind Windows containers are in beta on K8 no surprise there.


    Tuesday, May 15, 2018 4:56 PM
  • I remember the microsoft/windowsservercore:1803 image has patched with KB4103721.

    It works again after patching my Windows Server, version 1803 host.

    See:

    https://www.catalog.update.microsoft.com/Search.aspx?q=kb4103721


    Sic Parvis Magna

    Wednesday, May 16, 2018 1:04 AM
  • Have confirmed this is an issue with ACS engine, it has hard-coded values for one of the system containers that causes this. See the issue here - https://github.com/Azure/acs-engine/issues/2965

    Sam Cogan Microsoft Azure MVP
    Blog | Twitter

    • Marked as answer by SamCoganMVP Wednesday, May 16, 2018 8:01 AM
    Wednesday, May 16, 2018 8:01 AM