Overview Here is a list of the most common reported errors and how to solve them when using ZED Hub. Application Creation Missing application manifest No app.json manifest found. The application package (.zip file) is missing an app.json file describing your application. You can find a sample app.json file to modify for your own application in the application sample. Make sure that your application file is at the root of the ZIP file. Depending on the way they are created, ZIP files may contain a single folder at the root, however, the application package expects to have its files in the root directory. Tip: use edge_cli create_app to automatically generate this structure The application package is wrong or too large Applications must be .zip files under XX MB The uploaded application file must be a ZIP archive containing the files described in the application sample. The application archive can not be larger than a specific size. If your archive is too large, we recommend to minimize the number of embedded assets, avoid storing pre-compiled binary files in the archive and to build your application during the docker build phase. Tip: the best practice is to include most of your assets in your docker image Manifest found, but cannot be read Invalid app.json manifest file. The app.json manifest has been found in the application, but isn’t a valid JSON. Please verify the syntax of your JSON file manually or using a JSON parser, and try uploading your application again. Application Deployment Docker failed to connect network is unreachable Docker didn’t manage to connect to network resources, such as a docker registry. The network connection, the docker registry itself or a proxy in the middle might be experiencing issues. Check that you can pull regular docker images on your device, the status page of the docker registry, and if you are using a proxy, that nothing gets blocked. Device failed to download the application package An error occurred while downloading application resources. Not enough space left on application storage volume. The device didn’t manage to download the application package from the cloud. Make sure that disk space is available on your device’s application drive, and that there are no issues with its network connection. If this issue persists, check that you are able to download the specified release from the WEB interface and contact support. Device failed to extract the application package An error occurred while extracting application resources. An error occurred while creating application folder. The device has downloaded the application package by hasn’t managed to extract it (unzip). Make sure that disk space is available on your device’s application drive. If this issue persist, check that you are able to unzip the application package after downloading the specified release from ZED Hub and contact support. Device failed to load application twin metadata Invalid metadata in application resources. The device has failed to retrieve the application archive from the cloud. Your application may have been deleted from ZED Hub. We recommend trying to upload your application again and try deploying on your device. If this issue persists, check that you are able to download the specified release from ZED Hub and contact support. Malformed docker-compose file Malformated or unexisting docker-compose.yml. The docker-compose.yml file present in your application package is malformated or does not exist. You can check the validity of your docker-compose.yml file by running the command docker-compose config in the directory where your file is located. If this issue persists, check that you are able to download the specified release from ZED Hub, run docker-compose config at the root of the package content and contact support. Docker failed to pull images Requested access to the resource is denied Error response from daemon: server misbehaving. Error response from daemon: dial tcp: lookup Docker hasn’t managed to pull the images specified in the docker compose or Dockerfile, using docker-compose pull. You can check the details of that error by clicking on the error log in ZED Hub. This can occur when the docker registry you are pulling from needs authentication. To add a docker login, go to the Permissions section of your application in ZED Hub. This can also occur when the application storage disk does not have space left for the docker images you are pulling. Check that you can pull regular docker images on your device, the status page of the docker registry, and if you are using a proxy, that nothing gets blocked. Device failed to build an application An error occurred while executing docker-compose build. Docker hasn’t managed to build the application’s image from one of the Dockerfiles listed in the docker-compose.yml. Please check the details of that log to know the details of the problem, there may be an error in your Dockerfile. You can check the details of that error by clicking on the error log in ZED Hub. This can happen for many reasons, but you can build the image from your Dockerfile before deploying the application using docker build (and using qemu emulation if you are deploying to a different platform). If you are deploying your application on Jetson and run into this error : standard_init_linux.go:211: exec user process caused "exec format error" This probably means that you are deploying your application with the wrong architecture (like x86 instead of arm64). Device failed to start an application An error occurred while executing docker-compose up. Cannot run application. Docker hasn’t managed to create the container for your application when running docker-compose up. This can happen when the container stops right at the beginning of the execution or because of wrong docker-compose arguments in your docker-compose.yml. You can check the details of that error by clicking on the error log in ZED Hub. Please also check that the docker service is running on your device by running systemctl status docker or that your application storage isn’t full. If you are deploying your application on Jetson and run into this error : standard_init_linux.go:211: exec user process caused "exec format error" This probably means that you are deploying your application with the wrong architecture (like x86 instead of arm64). If this issue persists, copy the error log, and contact support. Device failed to stop an application An error occurred while executing docker-compose down. Cannot disable application. Docker hasn’t managed to stop the container for your application when running docker-compose down. You can check the details of that error by clicking on the error log in ZED Hub. Please check that the docker service is running on your device by running systemctl status docker. If this issue persists, copy the error log, and contact support. Device failed to remove an application Cannot remove application. Docker hasn’t managed to stop the container for your application when running docker-compose down or failed to remove your application directory. You can check the details of that error by clicking on the error log in ZED Hub. Please check that the docker service is running on your device by running systemctl status docker and that your application storage disk is not damaged. If this issue persists, copy the error log, and contact support. Application Runtime Application execution has been interrupted Application execution was interrupted. The application was successfully deployed, built and launched on the device, but its process exited with an error. This can be caused by a segmentation fault, an unhandled exception, or an intentional exit within your code. Please check the source code of your application, the console logs it has reported. If this is not enough to identify the cause, add some logs to get more information if it gets reproduced in the future. Then, restart the application on your device. Please note that according to the restart_policy you put in your application manifest, the application can be auto-restarted after its execution has been interrupted. If you are deploying your application on Jetson and run into this error : standard_init_linux.go:211: exec user process caused "exec format error" This probably means that you are deploying your application with the wrong architecture (like x86 instead of arm64).