Troubleshooting
This page is a collection of common problems and their solutions
auterion-cli app build exits with something similar to the output below:------
failed to solve: process "/dev/.buildkit_qemu_emulator /bin/sh -c mkdir build && cd build && cmake .. && make && cd .." did not complete successfully: exit code: 2
Docker compose build failed.
This means that there is an issue with the build of your docker app. In order to debug this, you can do the following steps:
- 1.Make sure that your app builds on your host platform, outside of docker. For this, manually invoke your build system in your source directory
- 2.Make sure the app builds with docker for your host platform. For this, go into the directory where your Dockerfile is and run
docker build . - 3.Make sure the app builds for linux/arm64 platform. For this, go into the directory where your Dockerfile is and run
docker build --platform=linux/arm64 .
In order to debug docker build issues, a useful technique often is to comment out the line that fails, and everything below it in the Dockerfile, then build the app and run it locally with an interactive shell like
docker run -it --rm --entrypoint=/bin/bash <hash of built image>. Then try to figure out why the build fails from this point on from within the container. If the installation of the app-base or your app terminates with
Waiting for the device to complete the installation
Expecting value: line 1 column 1 (char 0)
Waiting for the device to complete the installation
Expecting value: line 1 column 1 (char 0)
This means that the network connection with the device dropped before the installation finished on the device. The device still continues installation in that case. Recommendation is to leave the device for ~10 minutes, power-cycle it and test if the app is functional. If not, remove and re-install the app.
In case you get the message
Update verification failed. The system has been rollbacked
Internal error, failed to install application
This means that the system was unable to load your docker container and instantiate your service. This could be caused by a missing or corrupt app-base installation. Make sure you have the correct app-base installed.
Your app shows as constantly restarting
Name Version Status Enable Services Status Enable
---------------------------------- --------- ---------- -------- -------------------- ---------- ----------
com.auterion.test-app 0.0.1 restarting enabled test-app restarting restarting
This means that your app immediately crashes on startup. Make sure that the startup command in your Dockerfile is correct and that your app works properly.
In this case, often you can find the cause of the problem by looking at the logs of the app by running
auterion-cli app logs <app name> -fLast modified 2mo ago