Skip to content

1.1.2106.0 (Generally Available)
Compare
Choose a tag to compare
@fcabrera23 fcabrera23 released this 23 Jun 12:45
· 315 commits to main since this release
1.1.2106.0
07607d6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

⚠️ Important

If you are updating a device from the public preview version of IoT Edge for Linux on Windows to the generally available version, you need to uninstall and reinstall Azure IoT Edge. For more information, check AzEFLOW-Update.

Release Notes

  • Azure IoT Edge 1.1 LTS (version 1.1.3)
  • CBL Mariner (Linux Kernel version 5.10.37.1)
  • PowerShell Module to support installation and configuration
  • Provisioning (Manual) using connection string and X.509 certificates
  • Provisioning (Automatic - DPS) using symmetric keys, X.509 certificates, TPM attestation
  • GPU passthrough for Linux workloads (See: AzEFLOW-GPU for more information)

Resources

Changes from Public Preview

  • Azure EFLOW VM lifecycle management has changed and, as a result, is no longer available through Hyper-V Manager. Instead, please see PowerShell commands for managing the virtual machine.
  • Azure EFLOW Linux image no longer includes a package manager. The Linux environment is kept up to date using Windows Update. Please see AzEFLOW-Update for more information on updates.
  • Azure EFLOW Linux image migrated to a read-only root-fs and does not support adding custom packages to the Linux runtime.
  • Windows Admin Center (WAC) Azure IoT Edge extension updated to 1.61.0 to support new EFLOW GA functionalities – WAC IoT Edge extension remains in preview.
  • Remove EFLOW VM hostname final GUID and changed naming scheme to Windows host device name + "-EFLOW"

Known Issues

  • Trying to reboot the EFLOW VM from inside VM (sudo reboot / sudo shutdown –r now) will stop the VM but won't start it again. To reboot the VM, use PowerShell commands: Stop-Eflow and Start-Eflow.
  • When the host reboots after a feature update, it's possible that the wssdagent service won't start. Therefore, the user needs to manually start the service or reboot the host again to start the wssdagent service.
  • GPU-PV nvidia-container-cli: requirement error: unsatisfied condition: cuda>=11.2 - This issue is not specific to EFLOW. A workaround can be found on Step 11 of the guide: Run a GPU module on Microsoft Azure Stack Edge Pro GPU device/
  • EFLOW virtual machine creation failed when using Windows Server 2022 Public Preview.
Assets 2
Loading