Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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

Issue Analytics

State:
Created 5 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

8reactions

avranjucommented, Sep 27, 2018

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 <module id>” 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|01|rajave%40microsoft.com|27b24725fec74bb5b4dd08d624287bd9|72f988bf86f141af91ab2d7cd011db47|1|0|636736153608298042&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|01|rajave%40microsoft.com|27b24725fec74bb5b4dd08d624287bd9|72f988bf86f141af91ab2d7cd011db47|1|0|636736153608308053&sdata=PQfEGO%2FyvXWo6BAdhhWk9SjJyLUc31LescC32WtLbNs%3D&reserved=0.

3reactions

avranjucommented, Sep 27, 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)

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|01|rajave%40microsoft.com|5bad8e9586874098966f08d6242e335d|72f988bf86f141af91ab2d7cd011db47|1|0|636736178164102258&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|01|rajave%40microsoft.com|5bad8e9586874098966f08d6242e335d|72f988bf86f141af91ab2d7cd011db47|1|0|636736178164102258&sdata=%2BLTEoX1%2BGfvb9cwQEU7KPRccNSnVRzMHOHSgk1qjTeM%3D&reserved=0.