{"id":2074,"date":"2018-11-05T17:12:33","date_gmt":"2018-11-05T09:12:33","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/iotdev\/?p=2074"},"modified":"2019-02-15T10:27:05","modified_gmt":"2019-02-15T02:27:05","slug":"a-workaround-to-run-azure-iot-edge-on-arm64-devices","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/iotdev\/a-workaround-to-run-azure-iot-edge-on-arm64-devices\/","title":{"rendered":"A Workaround to Run Azure IoT Edge on ARM64 Devices"},"content":{"rendered":"

Azure IoT Edge went\u00a0generally available<\/a>\u00a0in June, with\u00a0official support<\/a>\u00a0for AMD64 and ARM32 platforms. Recently, more and more developers from the community requested to run Azure IoT Edge on ARM64 (a.k.a. AArch64) devices such NVIDIA TX2. While the ARM64 support of Azure IoT Edge is still in progress, this post will introduce a workaround.<\/p>\n

When we talk about “running Azure IoT Edge”, what we actually mean is running both the Azure IoT Edge security daemon (including its dependencies such as hsmlib) and the Azure IoT Edge runtime images (i.e., edgeAgent and edgeHub). As a result, the workaround requires changes to the official tutorial for these two parts.<\/p>\n

IoT Edge Security Daemon<\/h2>\n

To run IoT Edge security daemon on ARM64 devices, you need to\u00a0either<\/em>:<\/p>\n

    \n
  1. Install ARM32 (a.k.a., armhf) architecture Azure IoT Edge security daemon, hsmlib, and all their dependencies libs.\u00a0@marktayl1<\/a>\u00a0has provided installation steps in\u00a0this gist<\/a><\/li>\n
  2. Compile both Azure IoT Edge security daemon and hsmlib for ARM64 from source code, or use the pre-built binaries from the community (for example,\u00a0@vjrantal<\/a>\u00a0has provided pre-built 1.0.2 version)<\/li>\n<\/ol>\n

    Cross-compile IoT Edge Security Daemon and hsmlib for ARM64 on Linux AMD64 Machines<\/h3>\n
    \n

    You can skip this section if you would like to use pre-built binaries from the community.<\/p>\n<\/blockquote>\n

      \n
    1. Install\u00a0Docker-CE<\/a>, and follow\u00a0this tutorial<\/a>\u00a0to configure managing Docker as a non-root user<\/li>\n
    2. Install\u00a0rustup<\/a>:\u00a0curl https:\/\/sh.rustup.rs -sSf | sh<\/code>, and add Rust toolchain to\u00a0$PATH<\/code>:\u00a0source ~\/.cargo\/env<\/code><\/li>\n
    3. Clone the source code of IoT Edge OSS project:\u00a0$ git clone https:\/\/github.com\/Azure\/iotedge.git<\/code><\/li>\n
    4. $ cd iotedge\/edgelet\/build\/linux\/docker\/cross-compile<\/code><\/li>\n
    5. Build the container image with cross-compile toolchain:\u00a0$ ubuntu16.04\/build_arm64_toolchain_container.sh aarch64-unknown-linux-gnu<\/code><\/li>\n<\/ol>\n
      \n

      The above command targets ARM64 and Ubuntu 16.04. Read the\u00a0README<\/a>\u00a0file to learn about the commands targeting other OS such as Debian and Centos, as well as what tools are inside the build container.<\/p>\n<\/blockquote>\n

        \n
      1. $ cd ..\/..\/ubuntu16.04\/aarch64\/<\/code><\/li>\n
      2. $ chmod +x *.sh<\/code><\/li>\n
      3. Open\u00a0package-iotedged.sh<\/code>\u00a0and\u00a0package-libiothsm.sh<\/code>\u00a0in text editors, and comment the line with\u00a0docker pull \"$IMAGE\"<\/code><\/li>\n<\/ol>\n
        \n

        By default, the images built in Step 5 are tagged with a private registry which requires credentials to pull. By bypassing the\u00a0docker pull \"$IMAGE\"<\/code>\u00a0step we will always use the locally built ones.<\/p>\n<\/blockquote>\n

          \n
        1. Cross-compile hsmlib:\u00a0.\/package-libiothsm.sh<\/code><\/li>\n
        2. Cross-compile IoT Edge Security Daemon:\u00a0.\/package-iotedged.sh<\/code><\/li>\n<\/ol>\n

          IoT Edge Runtime Images<\/h2>\n

          For IoT Edge runtime images, edgeAgent (mcr.microsoft.com\/azureiotedge-agent:1.0<\/code>) and edgeHub (mcr.microsoft.com\/azureiotedge-hub:1.0<\/code>), the Docker tags are\u00a0multi-arch<\/a>. This means when you pull them on Linux AMD64 machines you get the Linux AMD64 variant, and when you pull them on ARM32 machines you get the ARM32 variant. However, these multi-arch tags don\u2019t support ARM64 yet. When you pull them on ARM64 machines, Docker daemon will try the find the ARM64 variant and finally get a 404 error. To workaround this, you need to explicitly specify the ARM32 variants, for example,\u00a0mcr.microsoft.com\/azureiotedge-agent:1.0.4-linux-arm32v7<\/code>\u00a0and\u00a0mcr.microsoft.com\/azureiotedge-hub:1.0.4-linux-arm32v7<\/code>.<\/p>\n

          Full Steps to Run the Simulated Temperature Sensor<\/h2>\n

          Here are the full steps I used to set up IoT Edge runtime on NVIDIA TX2 running Ubuntu 16.04 and deploy the simulated temperature sensor module (a.k.a., the Hello World for Azure IoT Edge):<\/p>\n

            \n
          1. Install Docker CE\n
            \n

            You may need to check the\u00a0Tegra-Docker<\/a>\u00a0project to learn how to enable Docker support on NVIDIA Tegra devices. Others from the community reported Moby also worked for them.<\/p>\n<\/blockquote>\n

              \n
            1. $ sudo apt-get update<\/code><\/li>\n
            2. $ sudo apt-get install apt-transport-https ca-certificates curl software-properties-common<\/code><\/li>\n
            3. $ curl -fsSL https:\/\/download.docker.com\/linux\/ubuntu\/gpg | sudo apt-key add -<\/code><\/li>\n
            4. $ sudo add-apt-repository \"deb [arch=arm64] https:\/\/download.docker.com\/linux\/ubuntu $(lsb_release -cs) stable\"<\/code><\/li>\n
            5. $ sudo apt-get update<\/code><\/li>\n
            6. $ sudo apt-get install docker-ce<\/code><\/li>\n
            7. Make sure Docker runs successfully:\u00a0$ sudo docker run hello-world<\/code><\/li>\n<\/ol>\n<\/li>\n
            8. Install the ARM64 IoT Edge daemon and hsmlib(here we take the 1.0.2 version pre-built by\u00a0@vjrantal<\/a>\u00a0for example)\n
                \n
              1. $ wget https:\/\/github.com\/vjrantal\/iot-edge-darknet-module\/files\/2423742\/iotedge-libiothsm-std-aarch64.zip<\/code><\/li>\n
              2. Unzip\u00a0iotedge-libiothsm-std-aarch64.zip<\/code><\/li>\n
              3. $ sudo apt-get install .\/libiothsm-std-1.0.2-aarch64.deb<\/code><\/li>\n
              4. $ sudo apt-get install .\/iotedge_1.0.2-1_aarch64.deb<\/code><\/li>\n<\/ol>\n<\/li>\n
              5. Create an IoT Hub<\/a><\/li>\n
              6. Create an IoT Edge device and retrieve the device connection string<\/a><\/li>\n
              7. Update IoT Edge Runtime configurations:\u00a0sudo vi \/etc\/iotedge\/config.yaml<\/code>\n
                  \n
                1. Set\u00a0provisioning<\/code>\u00a0->\u00a0device_connection_string<\/code>\u00a0with the device connection string retrieved in the last step<\/li>\n
                2. Set\u00a0agent<\/code>\u00a0->\u00a0config<\/code>\u00a0->\u00a0image<\/code>\u00a0with\u00a0mcr.microsoft.com\/azureiotedge-agent:1.0.4-linux-arm32v7<\/a><\/li>\n<\/ol>\n<\/li>\n
                3. Restart IoT Edge runtime:\u00a0$ sudo systemctl restart iotedge<\/code><\/li>\n
                4. Check IoT Edge runtime status:\u00a0$ sudo systemctl status iotedge<\/code>\u00a0\"\"<\/li>\n
                5. Deploy simulated temperature sensor module<\/a>\n
                    \n
                  1. In the 5th step of the above linked tutorial, use\u00a0mcr.microsoft.com\/azureiotedge-simulated-temperature-sensor:1.0.4-linux-arm32v7<\/code>\u00a0instead of\u00a0mcr.microsoft.com\/azureiotedge-simulated-temperature-sensor:1.0<\/code>.<\/li>\n
                  2. Before the 9th step of the above linked tutorial, click the \u201cConfigure advanced Edge runtime settings\u201d button\u00a0\"\"\n
                      \n
                    1. Set Edge Hub’s Image with\u00a0mcr.microsoft.com\/azureiotedge-hub:1.0.4-linux-arm32v7<\/code><\/li>\n
                    2. Set Edge Agent’s Image with\u00a0mcr.microsoft.com\/azureiotedge-agent:1.0.4-linux-arm32v7<\/code><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n
                    3. Wait for about a few seconds, check the status of edgeAgent, edgeHub and the simulated temperature sensor module\n
                        \n
                      1. $ sudo iotedge list<\/code>\u00a0\"\"<\/li>\n
                      2. $ sudo docker ps<\/code>\u00a0\"\"<\/li>\n
                      3. $ sudo docker logs -f <module_name><\/code>\u00a0to check module logs\uff0cfor example:\u00a0\"\"<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

                        Azure IoT Edge went\u00a0generally available\u00a0in June, with\u00a0official support\u00a0for AMD64 and ARM32 platforms. Recently, more and more developers from the community requested to run Azure IoT Edge on ARM64 (a.k.a. AArch64) devices such NVIDIA TX2. While the ARM64 support of Azure IoT Edge is still in progress, this post will introduce a workaround. When we talk […]<\/p>\n","protected":false},"author":536,"featured_media":2086,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[5,6,7,16,17,20],"class_list":["post-2074","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-iot-dev","tag-azure","tag-azure-iot","tag-azure-iot-hub","tag-internet-of-things","tag-iot","tag-iot-edge"],"acf":[],"blog_post_summary":"

                        Azure IoT Edge went\u00a0generally available\u00a0in June, with\u00a0official support\u00a0for AMD64 and ARM32 platforms. Recently, more and more developers from the community requested to run Azure IoT Edge on ARM64 (a.k.a. AArch64) devices such NVIDIA TX2. While the ARM64 support of Azure IoT Edge is still in progress, this post will introduce a workaround. When we talk […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/posts\/2074","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/users\/536"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/comments?post=2074"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/posts\/2074\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/media\/2086"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/media?parent=2074"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/categories?post=2074"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/iotdev\/wp-json\/wp\/v2\/tags?post=2074"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}