树莓派部署Azure IoT Edge时edgeHub模块无法启动的技术求助

运行环境 #

PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian

问题详情 #

• 最初运行Azure IoT Edge时edgeAgent启动失败，尝试sudo apt update、sudo apt upgrade等官方教程方法无效。
• 卸载IoT Edge并重新配置后，edgeAgent恢复正常，但edgeHub始终无法启动，甚至未拉取mcr.microsoft.com/azureiotedge-hub:1.4镜像对应的容器。
• 已尝试按单设备对称密钥配置流程重新部署，以及清理容器日志、停止并重建所有容器，问题仍未解决。

sudo iotedge check 日志输出 #

Configuration checks (aziot-identity-service)
---------------------------------------------
√ keyd configuration is well-formed - OK
√ certd configuration is well-formed - OK
√ tpmd configuration is well-formed - OK
√ identityd configuration is well-formed - OK
√ daemon configurations up-to-date with config.toml - OK
√ identityd config toml file specifies a valid hostname - OK
√ aziot-identity-service package is up-to-date - OK
√ host time is close to reference time - OK
√ preloaded certificates are valid - OK
√ keyd is running - OK
√ certd is running - OK
√ identityd is running - OK
√ read all preloaded certificates from the Certificates Service - OK
√ read all preloaded key pairs from the Keys Service - OK
√ check all EST server URLs utilize HTTPS - OK
√ ensure all preloaded certificates match preloaded private keys with the same ID - OK

Connectivity checks (aziot-identity-service)
--------------------------------------------
√ host can connect to and perform TLS handshake with iothub AMQP port - OK
√ host can connect to and perform TLS handshake with iothub HTTPS / WebSockets port - OK
√ host can connect to and perform TLS handshake with iothub MQTT port - OK

Configuration checks
--------------------
√ aziot-edged configuration is well-formed - OK
√ configuration up-to-date with config.toml - OK
√ container engine is installed and functional - OK
√ configuration has correct URIs for daemon mgmt endpoint - OK
√ aziot-edge package is up-to-date - OK
√ container time is close to host time - OK
‼ DNS server - Warning
    Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
    Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
    You can ignore this warning if you are setting DNS server per module in the Edge deployment.
‼ production readiness: logs policy - Warning
    Container engine is not configured to rotate module logs which may cause it run out of disk space.
    Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
    You can ignore this warning if you are setting log policy per module in the Edge deployment.
‼ production readiness: Edge Agent's storage directory is persisted on the host filesystem - Warning
    The edgeAgent module is not configured to persist its /tmp/edgeAgent directory on the host filesystem.
    Data might be lost if the module is deleted or updated.
    Please see https://aka.ms/iotedge-storage-host for best practices.
× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeHub container
√ Agent image is valid and can be pulled from upstream - OK
√ proxy settings are consistent in aziot-edged, aziot-identityd, moby daemon and config.toml - OK

Connectivity checks
-------------------
× container on the default network can connect to upstream AMQP port - Error
    Container on the default network could not connect to dc-hub-rnd.azure-devices.net:5671
× container on the default network can connect to upstream HTTPS / WebSockets port - Error
    Container on the default network could not connect to dc-hub-rnd.azure-devices.net:443
× container on the IoT Edge module network can connect to upstream AMQP port - Error
    Container on the azure-iot-edge network could not connect to dc-hub-rnd.azure-devices.net:5671
× container on the IoT Edge module network can connect to upstream HTTPS / WebSockets port - Error
    Container on the azure-iot-edge network could not connect to dc-hub-rnd.azure-devices.net:443
27 check(s) succeeded.
3 check(s) raised warnings. Re-run with --verbose for more details.
5 check(s) raised errors. Re-run with --verbose for more details.
2 check(s) were skipped due to errors from other checks. Re-run with --verbose for more details.

求助 #

请问还有其他方法可以让edgeHub正常运行吗？

从日志来看，核心问题是容器网络无法连接IoT Hub端口，结合edgeHub未启动的情况，可尝试以下步骤：

1. 手动拉取edgeHub镜像
   直接执行命令拉取指定版本镜像：

   sudo docker pull mcr.microsoft.com/azureiotedge-hub:1.4
   

   拉取完成后查看镜像是否存在：

   sudo docker images
   

2. 排查容器网络配置

   • 检查azure-iot-edge网络状态：

     sudo docker network inspect azure-iot-edge
     

   • 若网络异常，删除并重建网络：

     sudo docker network rm azure-iot-edge
     sudo iotedge restart
     

   • 配置Docker DNS服务器：编辑/etc/docker/daemon.json（不存在则创建），添加：

     {
       "dns": ["8.8.8.8", "8.8.4.4"]
     }
     

     保存后重启Docker和IoT Edge服务：

     sudo systemctl restart docker
     sudo iotedge restart
     

3. 配置edgeHub持久化存储

   • 在主机创建持久化目录并设置权限：

     sudo mkdir -p /iotedge/storage/edgeHub
     sudo chown 1000:1000 /iotedge/storage/edgeHub
     

   • 在Azure门户中更新edgeHub模块配置，将storageFolder参数指向该目录，重新应用部署配置。

4. 查看edgeAgent日志定位问题
   edgeAgent负责管理edgeHub启动，查看日志获取细节：

   sudo iotedge logs edgeAgent
   

   重点查找edgeHub拉取、启动阶段的错误信息，如认证失败、资源不足等。

5. 重置设备身份后重新配置
   若以上步骤无效，重置设备身份后重新走配置流程：

   sudo iotedge disconnect
   sudo iotedge config reset
   

内容的提问来源于stack exchange，提问作者Arseniy Sleptsov