Skip to content

Commit bfb3ad3

Browse files
authored
command update on pulling runtime container
Under the section "Store runtime containers in your private registry", the docker pull command "docker pull mcr.microsoft.com/azureiotedge-agent" is not accurate now. This command will auto refer to the version "latest", and it will fails to find the container as the "latest" version is not exist. suggested to change to "docker pull mcr.microsoft.com/azureiotedge-agent:[version]". and suggest user to find the latest version from azureiotedge-agent description page. This container has a latest version 1.0 which must be specified during pull, as I have checked that there is a policy changes of microsoft container version (please correct me if this is not the latest policy), that there will be no default "latest" version, and must specify the version number for every release.
1 parent 2f438fb commit bfb3ad3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/iot-edge/production-checklist.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -159,12 +159,12 @@ The IoT Edge agent and IoT Edge hub images are tagged with the IoT Edge version
159159

160160
You know about storing your container images for custom code modules in your private Azure registry, but you can also use it to store public container images such as for the edgeAgent and edgHub runtime modules. Doing so may be required if you have very tight firewall restrictions as these runtime containers are stored in the Microsoft Container Registry (MCR).
161161

162-
Obtain the images with the Docker pull command to place in your private registry. Be aware that you will need to update the images with each new release of IoT Edge runtime.
162+
Obtain the images with the Docker pull command to place in your private registry. You will need to specify the container version during the pull operation, find the latest container version at container description page as below, and replace the version in the pull command if needed. Be aware that you will need to update the images with each new release of IoT Edge runtime.
163163

164164
| IoT Edge runtime container | Docker pull command |
165165
| --- | --- |
166-
| [Azure IoT Edge Agent](https://hub.docker.com/_/microsoft-azureiotedge-agent) | `docker pull mcr.microsoft.com/azureiotedge-agent` |
167-
| [Azure IoT Edge Hub](https://hub.docker.com/_/microsoft-azureiotedge-hub) | `docker pull mcr.microsoft.com/azureiotedge-hub` |
166+
| [Azure IoT Edge Agent](https://hub.docker.com/_/microsoft-azureiotedge-agent) | `docker pull mcr.microsoft.com/azureiotedge-agent:1.0` |
167+
| [Azure IoT Edge Hub](https://hub.docker.com/_/microsoft-azureiotedge-hub) | `docker pull mcr.microsoft.com/azureiotedge-hub:1.0` |
168168

169169
Next, be sure to update the image references in the deployment.template.json file for the edgeAgent and edgeHub system modules. Replace `mcr.microsoft.com` with your registry name and server for both modules.
170170

0 commit comments

Comments
 (0)