CODEWITHSUNDEEP
azure-iot-edge
Terry Mandin
Terry Mandin

Reputation: 150

Error pulling edgeAgent from ACR with Windows container on IoT Edge v1.1

I am working with a customer using the v1.1 of IoT Edge with Windows containers. They are in a locked down environment and do not want to connect to a public container registry. They prefer to ingest from their own Azure Container Registry (ACR). We have copied edgeAgent and edgeHub from our public registry to ACR using az acr import to pull the containers from:

I am finding that Azure IoT Edge cannot download the edgeAgent image. If I download the edgeAgent container manually from ACR, edgeAgent will start will start correctly. edgeAgent will also be able to download and install edgeHub via ACR. eg.:

docker -H "npipe:////./pipe/iotedge_moby_engine" pull <private ACR>.azurecr.io/azureiotedge-agent:1.1

Any thoughts on why IoT Edge is unable to pull the image itself? Is there something wrong with my config.yaml configuration for edgeAgent?

agent:
  name: "edgeAgent"
  type: "docker"
  env: {}
  config:
    image: "<private ACR>.azurecr.io/azureiotedge-agent:1.1"
    auth:
      username: "<username>"
      password: "<key>"
      serveraddress: "<address>.azurecr.io"

Upvotes: 1

Views: 454

Answers (1)

Venkat Yalla
Venkat Yalla

Reputation: 558

allow-nondistributable-artifacts may be required. Please see

Note this setting is required on the docker daemon pushing the public images to the private registry, not the IoT Edge device itself.

If that doesn't help, I'd suggest opening an issue at https://github.com/azure/iotedge/issues and be sure to include logs from the iotedged service.

Upvotes: 1

Related Questions