Hello anonymous user I agree with your observation, and thanks for posting this question which is very helpful to others as well.
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
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.
Related question: Github
Please comment in the below section for feedback or comments.
If the response is helpful, please click "Accept Answer" and upvote it.