Iotedge: IoT Edge runtime is not downloading latest version of module image after its updated

Created on 27 Sep 2018 · 6Comments · Source: Azure/iotedge

Hi there,

I have an Azure IoT Edge device setup to pull an image from my Azure CR. It works fine and it pulls the latest image from the Azure CR. However, when I update this container on the Azure CR and push a new latest image. The Edge Runtime is not picking it up. Is this expected behavior?

Should I be setting modules by a specific tag name? I am thinking that using latest tag simplifies my deployment.json as I would not need to update it every time a new image is pushed.

Hope to hear from you soon.

Thanks
Has

customer-reported iotedge

Source

has-taiar

Most helpful comment

Hi Has,

Yes this behavior is by design. The Edge runtime is designed to detect changes in deployments. So if nothing has materially changed in the deployment definition itself (even if something referred to from the deployment — such as the image definition referred to by a tag — changes) then Edge does not take any action.

So we have a the following options:

Use a unique tag for every image
Change the “version” property in the module’s entry to a new value every time
Delete the module from the deployment and then add it back

Or if this is during development then you could simply run “docker rm -f ” and that should cause Edge to download the image afresh.

Raj

From: Has AlTaiar notifications@github.com
Sent: Wednesday, September 26, 2018 8:22:40 PM
To: Azure/iotedge
Cc: Subscribed
Subject: [Azure/iotedge] IoT Edge runtime is not downloading latest version of module image after its updated (#364)

Hi there,

I have an Azure IoT Edge device setup to pull an image from my Azure CR. It works fine and it pulls the latest image from the Azure CR. However, when I update this container on the Azure CR and push a new latest image. The Edge Runtime is not picking it up. Is this expected behavior?

Should I be setting modules by a specific tag name? I am thinking that using latest tag simplifies my deployment.json as I would not need to update it every time a new image is pushed.

Hope to hear from you soon.

Thanks
Has

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fiotedge%2Fissues%2F364&data=02%7C01%7Crajave%40microsoft.com%7C27b24725fec74bb5b4dd08d624287bd9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636736153608298042&sdata=76B6PFBFCVJr0uDXBiZB7aZsYnKtD34%2FogEdR2Psi88%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAmVoE9ohAqTLyswWT6DQHrpJldWwvHDks5ufESAgaJpZM4W714k&data=02%7C01%7Crajave%40microsoft.com%7C27b24725fec74bb5b4dd08d624287bd9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636736153608308053&sdata=PQfEGO%2FyvXWo6BAdhhWk9SjJyLUc31LescC32WtLbNs%3D&reserved=0.

avranju on 27 Sep 2018

👍4

All 6 comments

Hi Has,

So we have a the following options:

Use a unique tag for every image
Change the “version” property in the module’s entry to a new value every time
Delete the module from the deployment and then add it back

Or if this is during development then you could simply run “docker rm -f ” and that should cause Edge to download the image afresh.

Raj

Hi there,

Should I be setting modules by a specific tag name? I am thinking that using latest tag simplifies my deployment.json as I would not need to update it every time a new image is pushed.

Hope to hear from you soon.

Thanks
Has

avranju on 27 Sep 2018

👍4

Thanks for the prompt response @avranju, appreciate it.

Do we have to remove the image before we added it again? I am setting up CI/CD, so I am hoping that once an image is updated, it will trigger a new pipeline in Azure DevOps which would then just increment the tag (which would be version/build number). Would that be sufficient for the Edge Runtime to pull the new / latest image?

Thanks again

has-taiar on 27 Sep 2018

Yes that should be sufficient. Changing the tag in the deployment will cause Edge to detect the change and redeploy the module.

From: Has AlTaiar notifications@github.com
Sent: Wednesday, September 26, 2018 8:34:34 PM
To: Azure/iotedge
Cc: Raj Vengalil; Mention
Subject: Re: [Azure/iotedge] IoT Edge runtime is not downloading latest version of module image after its updated (#364)

Thanks for the prompt response @avranjuhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Favranju&data=02%7C01%7Crajave%40microsoft.com%7C9897d69427db450a7c1808d6242a2546%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636736160754406656&sdata=3TNoKoQP9uFD6Iglt7Z%2FwKwvEUDHFLJTk93YvrFBSME%3D&reserved=0, appreciate it.

Do we have to remove the image before we added it again? I am setting up CI/CD, so I am hoping that once an image is updated, it will trigger a new pipeline in Azure DevOps which would then just increment the tag (which would be version/build number). Would that be sufficient for the Edge Runtime to pull the new / latest image?

Thanks again

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fiotedge%2Fissues%2F364%23issuecomment-424947629&data=02%7C01%7Crajave%40microsoft.com%7C9897d69427db450a7c1808d6242a2546%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636736160754416664&sdata=vkpV%2FCUbm4aKIQcXaNzXi82E6xEg1UWSpUW6dc7UzKM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAmVoPcKcuTRXBJN_fx0i52Sl96Q2B0qks5ufEdKgaJpZM4W714k&data=02%7C01%7Crajave%40microsoft.com%7C9897d69427db450a7c1808d6242a2546%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636736160754416664&sdata=RQYhA5sIDHep%2BJa2G0uiLuiQBiz8uGrrxbK8D%2Fm5RmM%3D&reserved=0.

avranju on 27 Sep 2018

Thanks again @avranju,

Is that the best practice then? I was just concerned about updating the whole deployment.json file for one image as it might impact other modules inadvertently.

Thanks again for your quick reply. Much appreciated

has-taiar on 27 Sep 2018

Yes when image bits are updated it is a good practice to update the tag as well. And it should be safe to update the deployment, i.e., change just the tag for the module in question and leave all other module definitions in tact. Edge will only redeploy that one module that was updated.

Raj

From: Has AlTaiar notifications@github.com
Sent: Wednesday, September 26, 2018 9:03:36 PM
To: Azure/iotedge
Cc: Raj Vengalil; Mention
Subject: Re: [Azure/iotedge] IoT Edge runtime is not downloading latest version of module image after its updated (#364)

Thanks again @avranjuhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Favranju&data=02%7C01%7Crajave%40microsoft.com%7C5bad8e9586874098966f08d6242e335d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636736178164092248&sdata=TBH6w%2BzOzug0Nmjg%2BsTUgB2OyPrZGpJmne4ylUfZgjQ%3D&reserved=0,

Is that the best practice then? I was just concerned about updating the whole deployment.json file for one image as it might impact other modules inadvertently.

Thanks again for your quick reply. Much appreciated

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fiotedge%2Fissues%2F364%23issuecomment-424951521&data=02%7C01%7Crajave%40microsoft.com%7C5bad8e9586874098966f08d6242e335d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636736178164102258&sdata=omvNgfusBNbmp1%2BbW5ZlkAigQph5HAh%2BU%2F1dYMQ8NkM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAmVoCSh1KXyAzgBWH13KwlwrNvQlRo2ks5ufE4YgaJpZM4W714k&data=02%7C01%7Crajave%40microsoft.com%7C5bad8e9586874098966f08d6242e335d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636736178164102258&sdata=%2BLTEoX1%2BGfvb9cwQEU7KPRccNSnVRzMHOHSgk1qjTeM%3D&reserved=0.

avranju on 27 Sep 2018

👍2

I'm going to close this issue because it seems to have been resolved. Please feel free to reopen if this is not the case. Thanks.