Question on support for version mismatch of IotEdge security subsystem and runtime containers (edgeAgent, edgeHub)

Question

Question on support for version mismatch of IotEdge security subsystem and runtime containers (edgeAgent, edgeHub)

Michael Moles 25

Documentation says "While mismatched versions are supported, we haven't tested all version combinations." I know that implies 1.5.0 with 1.5.19 runtime containers is supported, but is 1.0.10 with 1.5 runtime containers supported, just untested?

I ask because it's easy and fairly safe to update the runtime containers, but the security subsystem is very problematic or not possible. If your running an older Linux OS like debian-stretch, 1.1.15 is last security subsystem released for it.

https://docs.azure.cn/en-us/iot-edge/how-to-update-iot-edge?view=iotedge-1.5&tabs=linux#verify-versions-match

VSawhney 800 Reputation points Microsoft External Staff Moderator

2025-04-21T06:55:58.0766667+00:00

Hello Michael Moles,

Hope the pointers by Sander van de Velde | MVP cleared your doubts on compatibility. Please check supported OS for reference.
IoT Edge supported platforms | Azure Docs

Thank you!

Accepted answer

0 additional answers

Your answer

VSawhney 800 Reputation points Microsoft External Staff Moderator

2025-04-21T06:55:58.0766667+00:00

Hello Michael Moles,

Hope the pointers by Sander van de Velde | MVP cleared your doubts on compatibility. Please check supported OS for reference.
IoT Edge supported platforms | Azure Docs

Thank you!

Answer 1

Sander van de Velde | MVP 36,766 MVP Volunteer Moderator

Hello @Michael Moles ,

welcome to this moderated Azure community forum.

It's possible to reuse custom modules written in the past for 1.1 in 1.5.

For C# modules, the only change for them is that old ModuleClient code libraries are used and an old .Net version is used to build the modules.

For the EdgeAgent and EdgeHub, it's better to keep them on par.

I have not experimented with this much but indeed this can complicate things.

Perhaps you get away with mixing version 1.4 and version 1.5 but version 1.2 and especially version 1.1 will cause a lot a lot of problems.

If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.

Michael Moles 25 Reputation points

2025-04-24T15:26:31.98+00:00

Perhaps you get away with mixing version 1.4 and version 1.5 but version 1.2 and especially version 1.1 will cause a lot a lot of problems.

If i keep the library up to date and use 1.5 runtime, what kind of problems could I expect when running 1.0 or 1.1 subsystem? Currently, my modules seem to work fine, but i didn't look into the status of the security subsystem or runtime containers.
Michael Moles 25 Reputation points

2025-04-24T15:28:42.4733333+00:00

I accidently did the previous one as an answer and converted it to a comment, just posting this to make sure the notifications fire off that there was a response.
Sander van de Velde | MVP 36,766 Reputation points MVP Volunteer Moderator

2025-04-24T16:25:12.3566667+00:00

Hello @Michael Moles ,

Perhaps you get away with mixing version 1.4 and version 1.5 but version 1.2 and especially version 1.1 will cause a lot a lot of problems.

This is related to the EdgeAgent And EdgeHub modules. I have never tested the newer versions with the 1.0/1.1 subsystem. If this works in your case, you are lucky :-)

As a rule of thumb, I keep the version on par with the runtime version. This way, you will also get support from Microsoft in case something breaks. Microsoft is not really happy with issues on systems where the versions are not on par.

Regarding custom modules, the only issue I see is that the SDKs used will get older where newer SDK versions get bug fixes and security patches.

Share via

Question on support for version mismatch of IotEdge security subsystem and runtime containers (edgeAgent, edgeHub)

0 additional answers

Your answer