none
Insufficient system resources exist to complete the requested service since KB457006 RRS feed

  • Question

  • We have Azure IoT Edge installed on two Windows Server 2019 Datacenter 1809 (Build 17763.1457) which were working correctly before the KB457006 update. Since the update installation we are getting the error "Insufficient system resources exist to complete the requested service" when starting the Edge Agent docker image.

    For reference, here's the result of iotedge check that shows the docker error.

    PS P:\> iotedge check
    Configuration checks
    --------------------
    √ config.yaml is well-formed - OK
    √ config.yaml has well-formed connection string - OK
    √ container engine is installed and functional - OK
    √ Windows host version is supported - OK
    √ config.yaml has correct hostname - OK
    × config.yaml has correct URIs for daemon mgmt endpoint - Error
        Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.0.9.5' locally
        1.0.9.5: Pulling from azureiotedge-diagnostics
        6a5e981230da: Pulling fs layer
        f7de0eb29689: Pulling fs layer
        b9472b5cda4b: Pulling fs layer
        b9472b5cda4b: Verifying Checksum
        b9472b5cda4b: Download complete
        6a5e981230da: Verifying Checksum
        6a5e981230da: Download complete
        f7de0eb29689: Verifying Checksum
        f7de0eb29689: Download complete
        6a5e981230da: Pull complete
        f7de0eb29689: Pull complete
        b9472b5cda4b: Pull complete
        Digest: sha256:b56d76881cad70d73106099510acdfb32f78b62e109d62996c4a71a53e3d3f7c
        Status: Downloaded newer image for mcr.microsoft.com/azureiotedge-diagnostics:1.0.9.5
        docker: Error response from daemon: hcsshim::CreateComputeSystem d1e446a8b63c01dee5da6bfc3cf4e1e67258fba5f850cbff22fd5e28bb39115d: Insufficient system resources exist to complete the requested service.
        (extra info: {"SystemType":"Container","Name":"d1e446a8b63c01dee5da6bfc3cf4e1e67258fba5f850cbff22fd5e28bb39115d","Owner":"docker","VolumePath":"\\\\?\\Volume{7acefee5-2633-413c-bd11-dd1f37fc09ca}","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\iotedge-moby\\windowsfilter\\d1e446a8b63c01dee5da6bfc3cf4e1e67258fba5f850cbff22fd5e28bb39115d","Layers":[{"ID":"1fba2e47-c004-5a7d-8764-d8a42b59dfe1","Path":"C:\\ProgramData\\iotedge-moby\\windowsfilter\\95283b53a8b32d1088ac51fa06caa159b706d6778d3cfe5d045b56576b02c85b"},{"ID":"fa14c24e-51b7-5e54-9c23-ddc1fa1df49e","Path":"C:\\ProgramData\\iotedge-moby\\windowsfilter\\7761baa93e1f611b78d9d14bf0bee05c54c10bbffab00bfa309c571bfb4aa072"},{"ID":"b5428c02-c8fe-5bb0-b469-77eb2965a34d","Path":"C:\\ProgramData\\iotedge-moby\\windowsfilter\\ea1789788090b5634d53bf3e3615c7b2ffe9e994f8fa9932076a4adffc9f3126"}],"HostName":"d1e446a8b63c","MappedDirectories":[{"HostPath":"c:\\programdata\\iotedge\\mgmt","ContainerPath":"c:\\programdata\\iotedge\\mgmt","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0,"CreateInUtilityVM":false}],"HvPartition":false,"EndpointList":["30ADC2FD-A576-4E70-915B-47A8168400C2"],"AllowUnqualifiedDNSQuery":true}).
    √ latest security daemon - OK
    ‼ host time is close to real time - Warning
        Could not query NTP server
    × container time is close to host time - Error
        Could not query local time inside container
    ‼ DNS server - Warning
        Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
        Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
        You can ignore this warning if you are setting DNS server per module in the Edge deployment.
    ‼ production readiness: certificates - Warning
        The Edge device is using self-signed automatically-generated development certificates.
        They will expire in 89 days (at 2021-01-06 12:07:44 UTC) causing module-to-module and downstream device communication to fail on an active deployment.
        After the certs have expired, restarting the IoT Edge daemon will trigger it to generate new development certs.
        Please consider using production certificates instead. See https://aka.ms/iotedge-prod-checklist-certs for best practices.
    √ production readiness: container engine - OK
    ‼ production readiness: logs policy - Warning
        Container engine is not configured to rotate module logs which may cause it run out of disk space.
        Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
        You can ignore this warning if you are setting log policy per module in the Edge deployment.
    ‼ production readiness: Edge Agent's storage directory is persisted on the host filesystem - Warning
        The edgeAgent module is not configured to persist its C:\Windows\Temp\edgeAgent directory on the host filesystem.
        Data might be lost if the module is deleted or updated.
        Please see https://aka.ms/iotedge-storage-host for best practices.
    × production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error
        Could not check current state of edgeHub container
    
    Connectivity checks
    -------------------
    √ host can connect to and perform TLS handshake with IoT Hub AMQP port - OK
    √ host can connect to and perform TLS handshake with IoT Hub HTTPS / WebSockets port - OK
    √ host can connect to and perform TLS handshake with IoT Hub MQTT port - OK
    × container on the IoT Edge module network can connect to IoT Hub AMQP port - Error
        Container on the nat network could not connect to IotixHub.azure-devices.net:5671
    × container on the IoT Edge module network can connect to IoT Hub HTTPS / WebSockets port - Error
        Container on the nat network could not connect to IotixHub.azure-devices.net:443
    × container on the IoT Edge module network can connect to IoT Hub MQTT port - Error
        Container on the nat network could not connect to IotixHub.azure-devices.net:8883
    
    10 check(s) succeeded.
    5 check(s) raised warnings. Re-run with --verbose for more details.
    6 check(s) raised errors. Re-run with --verbose for more details.

    The explanation in the KB457006 tells that this error might arrive when the virtual machine is using RemoteFX, but I don't think that this is an option we can change in the docker container?

    For reference, I have opened an issue on the IoT Edge GitHub and was told that this might be more of a Windows Container issue and to post here. https://github.com/Azure/iotedge/issues/3680

    Thanks in advance for your help.

    Friday, October 9, 2020 8:30 AM

All replies

  • did you get any solution to this problem ? same here

    https://stackoverflow.com/questions/64085411/build-or-run-docker-image-error-createcomputesystem-insufficient-system-reso

    Monday, October 12, 2020 3:49 PM