Hello @Omar Navarro ,
What is the tag of the module image , are you using it?
A tag is a docker concept that you can use to distinguish between versions of docker containers. Tags are suffixes like 1.1 that go on the end of a container repository. For example, mcr.microsoft.com/azureiotedge-agent:1.1. Tags are mutable and can be changed to point to another container at any time, so your team should agree on a convention to follow as you update your module images moving forward.
Tags also help you to enforce updates on your IoT Edge devices. When you push an updated version of a module to your container registry, increment the tag. Then, push a new deployment to your devices with the tag incremented. The container engine will recognize the incremented tag as a new version and will pull the latest module version down to your device.
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.
Also Refer to similar: Link
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.
If the response is helpful, please click "Accept Answer" and upvote it. So that we can close this thread.