In this post I would like to show some tweaks you can (and might need to) apply to influence the behavior of your IoT Edge device, when it comes to message retention on devices that are limited in resources.
The setup of this scenario is not uncommon, as it uses a module to retrieve telemetry from machines, parses them in another module and sends the messages to an IoT Hub.
Sometimes a permission denied is a permission denied 🙁
[INFO] - Starting Azure IoT Edge Security Daemon<br>[INFO] - Version - 1.0.10~rc1<br>[INFO] - Using config file: /etc/iotedge/config.yaml<br>[INFO] - Configuring /var/lib/iotedge as the home directory.<br>[INFO] - Configuring certificates…<br>[INFO] - Transparent gateway certificates not found, operating in quick start mode…<br>[INFO] - Finished configuring provisioning environment variables and certificates.<br>[INFO] - Initializing hsm…<br>[INFO] - Finished initializing hsm.<br>[INFO] - Provisioning edge device…<br>[INFO] - Starting provisioning edge device via manual mode using a device connection string…<br>[INFO] - Manually provisioning device "iotedgedevice" in hub "iothub.azure-devices.net"<br>[INFO] - Finished provisioning edge device.<br>[INFO] - Initializing the module runtime…<br>[INFO] - Initializing module runtime…<br>[INFO] - Using runtime network id azure-iot-edge<br>[WARN] - Could not initialize module runtime<br>[WARN] - caused by: Container runtime error<br>[WARN] - caused by: error trying to connect: Permission denied (os error 13)<br>[ERR!] - The daemon could not start up successfully: Could not initialize module runtime<br>[ERR!] - caused by: Could not initialize module runtime<br>[ERR!] - caused by: Container runtime error<br>[ERR!] - caused by: error trying to connect: Permission denied (os error 13)
