New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IoT Edge runtime is not downloading latest version of module image after its updated #364
Comments
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:
1. Use a unique tag for every image
2. Change the “version” property in the module’s entry to a new value every time
3. 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 GitHub<https://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 thread<https://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>.
|
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 Thanks again |
Thanks again @avranju, Is that the best practice then? I was just concerned about updating the whole Thanks again for your quick reply. Much appreciated |
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. |
There is one setting while deploying the custom iot edge module that is Image Pull Policy. But there is no option to use always. Now what I need to handle scenario as @has-taiar ,If I push any changes to azure container registry it will not reflect in my iot edge device. So iot edge agent automatically detect that changes or how can I handle this type of scenario? |
Hi there,
I have an Azure IoT Edge device setup to
pull
an image from myAzure CR
. It works fine and it pulls thelatest
image from theAzure CR
. However, when I update this container on theAzure CR
and push a newlatest
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 mydeployment.json
as I would not need to update it every time a new image is pushed.Hope to hear from you soon.
Thanks
Has
The text was updated successfully, but these errors were encountered: