You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-edge/how-to-update-iot-edge.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Use the sections of this article to update both the security subsystem and runti
30
30
31
31
### Patch releases
32
32
33
-
When you upgrade between *patch* releases, for example 1.4.1 to 1.4.2, the update order isn't important. You can upgrade the security subsystem or the runtime containers before or after the other. To update between patch releases:
33
+
When you upgrade between *patch* releases, for example 1.5.1 to 1.5.2, the update order isn't important. You can upgrade the security subsystem or the runtime containers before or after the other. To update between patch releases:
34
34
35
35
1.[Update the security subsystem](#update-the-security-subsystem)
36
36
1.[Update the runtime containers](#update-the-runtime-containers)
@@ -48,7 +48,7 @@ When you upgrade between major or minor releases, for example from 1.4 to 1.5, u
48
48
49
49
1. On the device, [install IoT Edge](how-to-provision-single-device-linux-symmetric.md#install-iot-edge).
50
50
51
-
If you're importing an old configuration using `iotedge config import`, then modify the [agent.config] image of the generated `/etc/aziot/config.toml` file to use the 1.4 image for edgeAgent.
51
+
If you're importing an old configuration using `iotedge config import`, then modify the [agent.config] image of the generated `/etc/aziot/config.toml` file to use the 1.5 image for edgeAgent.
52
52
53
53
For more information, see [Configure IoT Edge device settings](configure-device.md#default-edge-agent).
54
54
@@ -160,7 +160,7 @@ The IoT Edge service pulls the latest versions of the runtime images and automat
160
160
161
161
### Update a specific tag image
162
162
163
-
If you use specific tags in your deployment (for example, mcr.microsoft.com/azureiotedge-hub:**1.4**) then all you need to do is update the tag in your deployment manifest and apply the changes to your device.
163
+
If you use specific tags in your deployment (for example, mcr.microsoft.com/azureiotedge-hub:**1.5**) then all you need to do is update the tag in your deployment manifest and apply the changes to your device.
164
164
165
165
1. In the IoT Hub in the Azure portal, select your IoT Edge device, and select **Set Modules**.
166
166
@@ -190,9 +190,9 @@ If you use partner modules, update your module deployments with image URIs provi
190
190
191
191
## Verify versions match
192
192
193
-
1. On your device, use `iotedge version` to check the security subsystem version. The output includes the major, minor, and revision version numbers. For example, *iotedge 1.4.2*.
193
+
1. On your device, use `iotedge version` to check the security subsystem version. The output includes the major, minor, and revision version numbers. For example, *iotedge 1.5.15*.
194
194
195
-
1. In your device deployment runtime settings, verify the *edgeHub* and *edgeAgent* image URI versions match the major and minor version of the security subsystem. If the security subsystem version is 1.4.2, the image versions would be 1.4. For example, *mcr.microsoft.com/azureiotedge-hub:1.4* and *mcr.microsoft.com/azureiotedge-agent:1.4*.
195
+
1. In your device deployment runtime settings, verify the *edgeHub* and *edgeAgent* image URI versions match the major and minor version of the security subsystem. If the security subsystem version is 1.5.15, the image versions would be 1.5. For example, *mcr.microsoft.com/azureiotedge-hub:1.5* and *mcr.microsoft.com/azureiotedge-agent:1.5*.
196
196
197
197
>[!NOTE]
198
198
>Update the IoT Edge security subsystem and runtime containers to the same supported release version. While mismatched versions are supported, we haven't tested all version combinations.
This article explains what operating system platforms, IoT Edge runtimes, container engines, and components are supported by IoT Edge whether generally available or in preview.
17
17
@@ -52,22 +52,6 @@ Modules built as Linux containers can be deployed to either Linux or Windows dev
52
52
53
53
[IoT Edge for Linux on Windows](iot-edge-for-linux-on-windows.md) is the recommended way to run IoT Edge on Windows devices.
54
54
55
-
::: moniker range="=iotedge-1.4"
56
-
57
-
| Operating System | AMD64 | ARM32v7 | ARM64 | End of OS provider standard support |
|[Red Hat Enterprise Linux 9](https://access.redhat.com/articles/3078)||||[May 2032](https://access.redhat.com/product-life-cycles?product=Red%20Hat%20Enterprise%20Linux,OpenShift%20Container%20Platform%204)|
61
-
|[Red Hat Enterprise Linux 8](https://access.redhat.com/articles/3078)||||[May 2029](https://access.redhat.com/product-life-cycles?product=Red%20Hat%20Enterprise%20Linux,OpenShift%20Container%20Platform%204)|
62
-
|[Ubuntu Server 22.04](https://wiki.ubuntu.com/JammyJellyfish/ReleaseNotes)||||[June 2027](https://wiki.ubuntu.com/Releases)|
63
-
|[Ubuntu Server 20.04](https://wiki.ubuntu.com/FocalFossa/ReleaseNotes)||||[April 2025](https://wiki.ubuntu.com/Releases)|
64
-
|[Windows 10/11](iot-edge-for-linux-on-windows.md#prerequisites)|||| See [Azure IoT EFLOW](iot-edge-for-linux-on-windows.md#prerequisites) for supported Windows OS versions. |
65
-
|[Windows Server 2019/2022](iot-edge-for-linux-on-windows.md#prerequisites)|||| See [Azure IoT EFLOW](iot-edge-for-linux-on-windows.md#prerequisites) for supported Windows OS versions. |
66
-
67
-
::: moniker-end
68
-
69
-
::: moniker range=">=iotedge-1.5"
70
-
71
55
| Operating System | AMD64 | ARM32v7 | ARM64 | End of OS provider standard support |
@@ -83,8 +67,6 @@ Modules built as Linux containers can be deployed to either Linux or Windows dev
83
67
84
68
<sup>1</sup> Ubuntu Core is fully supported but the automated testing of Snaps currently happens on Ubuntu 22.04 Server LTS.
85
69
86
-
::: moniker-end
87
-
88
70
> [!NOTE]
89
71
> When a *Tier 1* operating system reaches its end of standard support date, it's removed from the *Tier 1* supported platform list. If you take no action, IoT Edge devices running on the unsupported operating system continue to work but ongoing security patches and bug fixes in the host packages for the operating system won't be available after the end of support date. To continue to receive support and security updates, we recommend that you update your host OS to a *Tier 1* supported platform.
90
72
@@ -101,32 +83,6 @@ The systems listed in the following table are considered compatible with Azure I
101
83
>
102
84
> Installation packages are made available on the [Azure IoT Edge releases](https://github.com/Azure/azure-iotedge/releases). See the installation steps in [Offline or specific version installation](how-to-provision-single-device-linux-symmetric.md#offline-or-specific-version-installation-optional).
103
85
104
-
105
-
::: moniker range="=iotedge-1.4"
106
-
107
-
| Operating System | AMD64 | ARM32v7 | ARM64 | End of OS provider standard support |
|[CentOS-7](https://docs.centos.org/en-US/docs/)||||[June 2024](https://www.redhat.com/en/topics/linux/centos-linux-eol). For more information, see the [CentOS End Of Life guidance](/azure/virtual-machines/workloads/centos/centos-end-of-life). |
|[Mentor Embedded Linux Flex OS](https://www.mentor.com/embedded-software/linux/mel-flex-os/)|||||
113
-
|[Mentor Embedded Linux Omni OS](https://www.mentor.com/embedded-software/linux/mel-omni-os/)|||||
|[Wind River 8](https://docs.windriver.com/category/os-wind_river_linux)|||||
119
-
|[Yocto (kirkstone)](https://www.yoctoproject.org/)<br>For Yocto issues, open a [GitHub issue](https://github.com/Azure/meta-iotedge/issues)||||[April 2026](https://wiki.yoctoproject.org/wiki/Releases)|
120
-
| Raspberry Pi OS Buster ||||[June 2024](https://wiki.debian.org/LTS)|
121
-
122
-
<sup>1</sup> With the release of 1.3, there are new system calls that cause crashes in Debian 10. To see the workaround, view the [Known issue: Debian 10 (Buster) on ARMv7](https://github.com/Azure/azure-iotedge/releases) section of the 1.3 release notes for details.
123
-
124
-
<sup>2</sup> Ubuntu Core is fully supported but the automated testing of Snaps currently happens on Ubuntu 22.04 Server LTS.
125
-
126
-
::: moniker-end
127
-
128
-
::: moniker range=">=iotedge-1.5"
129
-
130
86
| Operating System | AMD64 | ARM32v7 | ARM64 | End of OS provider standard support |
@@ -139,8 +95,6 @@ The systems listed in the following table are considered compatible with Azure I
139
95
|[Yocto (scarthgap)](https://www.yoctoproject.org/)<br>For Yocto issues, open a [GitHub issue](https://github.com/Azure/meta-iotedge/issues)||||[April 2028](https://wiki.yoctoproject.org/wiki/Releases)|
140
96
|[Yocto (kirkstone)](https://www.yoctoproject.org/)<br>For Yocto issues, open a [GitHub issue](https://github.com/Azure/meta-iotedge/issues)||||[April 2026](https://wiki.yoctoproject.org/wiki/Releases)|
141
97
142
-
::: moniker-end
143
-
144
98
> [!NOTE]
145
99
> When a *Tier 2* operating system reaches its end of standard support date, it's removed from the supported platform list. If you take no action, IoT Edge devices running on the unsupported operating system continue to work but ongoing security patches and bug fixes in the host packages for the operating system won't be available after the end of support date. To continue to receive support and security updates, we recommend that you update your host OS to a *Tier 1* supported platform.
Copy file name to clipboardExpand all lines: articles/iot-edge/tutorial-develop-for-linux-on-windows.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -263,7 +263,7 @@ The deployment template includes:
263
263
264
264
### Set the IoT Edge runtime version
265
265
266
-
Currently, the latest stable runtime version is 1.4. Update the IoT Edge runtime version to the latest stable release or the version that you want to target for your devices:
266
+
Currently, the latest stable runtime version is 1.5. Update the IoT Edge runtime version to the latest stable release or the version that you want to target for your devices:
267
267
268
268
::: zone pivot="iotedge-dev-ext"
269
269
@@ -273,17 +273,17 @@ Currently, the latest stable runtime version is 1.4. Update the IoT Edge runtime
273
273
274
274
1. Use the dropdown menu to choose the runtime version that your IoT Edge devices are running. Then select **OK** to save your changes. If you didn't make any changes, select **Cancel**.
275
275
276
-
Currently, the extension doesn't include a selection for the latest runtime versions. If you want to set the runtime version higher than 1.2, open the `deployment.debug.template.json` deployment manifest file. Change the runtime version for the system runtime module images `edgeAgent` and `edgeHub`. For example, if you want to use the IoT Edge runtime version 1.4, change the following lines in the deployment manifest file:
276
+
Currently, the extension doesn't include a selection for the latest runtime versions. If you want to set the runtime version higher than 1.2, open the `deployment.debug.template.json` deployment manifest file. Change the runtime version for the system runtime module images `edgeAgent` and `edgeHub`. For example, if you want to use the IoT Edge runtime version 1.5, change the following lines in the deployment manifest file:
@@ -294,17 +294,17 @@ Currently, the latest stable runtime version is 1.4. Update the IoT Edge runtime
294
294
::: zone pivot="iotedge-dev-cli"
295
295
296
296
1. Open the `deployment.debug.template.json` deployment manifest file.
297
-
1. Change the runtime version for the system runtime module images `edgeAgent` and `edgeHub`. For example, if you want to use IoT Edge runtime version 1.4, change the following lines in the deployment manifest file:
297
+
1. Change the runtime version for the system runtime module images `edgeAgent` and `edgeHub`. For example, if you want to use IoT Edge runtime version 1.5, change the following lines in the deployment manifest file:
0 commit comments