Using ZED Hub to deploy (install) body(skeleton) tracking fails with an error

Hardware ZED2
1

I am attempting to deploy the skeleton tracker through the zed hub. and it fails with the following error. Feels like I am missing some documentation reference which version to install.

Thank your help!

Error Log:

[Info] [2023/12/Fr 08:10:27 pm] Waiting for device to start the operation...
[Info] [2023/12/Fr 08:10:33 pm] Downloading application Edge Body Tracking 0.1.8...
[Info] [2023/12/Fr 08:10:33 pm] Deploy Edge Body Tracking 0.1.8.
[Info] [2023/12/Fr 08:10:34 pm] Application Edge Body Tracking 0.1.8 downloaded successfully.
[Error] [2023/12/Fr 08:10:34 pm] Cannot deploy application. L4T R35.4 is not supported by the application.

System Details:

Host
Product
Details:
Product
desktop

Operating System
Ubuntu 20.04.6 LTS

Kernel version
5.10.120-tegra

L4T release
L4T R35.4.1

CPU model
ARMv8 Processor rev 1 (v8l) (aarch64)

GPU model
OrinAmpere

CPU memory
6 GB

GPU memory
6 GB

NVP model
15W

Original Post

2

Hi @daGoedie,
Edge Body Tracking v0.1.8 is not compatible with L4T35.4.
ZED Hub is compatible with L4T35.4 but we did not deploy a new version of Edge Body Tracking yet.

We will deploy a compatible version ASAP.
Sorry for the delay.

1 Like
3

Hi @daGoedie,

Edge Body Tracking v0.1.9 has been deployed and is compatible with L4T35.4.
You can update Edge Body Tracking.

1 Like
4

Hey @fjiang,

Thanks for the update. I tried to run it and now run into another error. I feel maybe I didnt setup the zed-hub correctly. Any ideas:

[Info] [2023/12/Mo 06:31:55 pm] Waiting for device to start the operation...
[Info] [2023/12/Mo 06:32:00 pm] Restart Edge Body Tracking 0.1.9.
[Info] [2023/12/Mo 06:32:00 pm] Starting build for application Edge Body Tracking 0.1.9...
[Error] [2023/12/Mo 06:33:34 pm] Cannot run application. An error occured while executing docker-compose build.

new Logs after restart:

[Info] [2023/12/11, 13:14:16] Application Edge Body Tracking 0.1.9 downloaded successfully....
[Info] [2023/12/11, 13:14:21] build for application Edge Body Tracking 0.1.9...
[Build] [2023/12/11, 13:14:25] Building edge_body_tracking_service
[Build] [2023/12/11, 13:14:26] Step 1/15 : ARG BUILD_IMAGE
[Build] [2023/12/11, 13:14:26] Step 2/15 : ARG RUNTIME_IMAGE
[Build] [2023/12/11, 13:14:26] Step 3/15 : FROM ${BUILD_IMAGE} as builder
[Build] [2023/12/11, 13:15:13] ERROR: Service 'edge_body_tracking_service' failed to build: Get https://registry-1.docker.io/v2/stereolabs/iot/manifests/sha256:54f927d254bc6d067a2caedc639eb74039b9fd5f415b7a0d490daf3db8d58baf: net/http: TLS handshake timeout
[Build] [2023/12/11, 13:15:19] Building edge_body_tracking_service
[Build] [2023/12/11, 13:15:20] Step 1/15 : ARG BUILD_IMAGE
[Build] [2023/12/11, 13:15:20] Step 2/15 : ARG RUNTIME_IMAGE
[Build] [2023/12/11, 13:15:20] Step 3/15 : FROM ${BUILD_IMAGE} as builder
[Build] [2023/12/11, 13:15:47] ERROR: Service 'edge_body_tracking_service' failed to build: Head https://registry-1.docker.io/v2/stereolabs/iot/manifests/0.73.2-devel-jetson-l4t35.4-zed4.0: Get https://auth.docker.io/token?scope=repository%3Astereolabs%2Fiot%3Apull&service=registry.docker.io: dial tcp: lookup auth.docker.io on 127.0.0.53:53: read udp 127.0.0.1:52974->127.0.0.53:53: i/o timeout
[Build] [2023/12/11, 13:15:53] Building edge_body_tracking_service
[Build] [2023/12/11, 13:15:54] Step 1/15 : ARG BUILD_IMAGE
[Build] [2023/12/11, 13:15:54] Step 2/15 : ARG RUNTIME_IMAGE
[Build] [2023/12/11, 13:15:54] Step 3/15 : FROM ${BUILD_IMAGE} as builder
[Build] [2023/12/11, 13:16:16] ERROR: Service 'edge_body_tracking_service' failed to build: Get https://registry-1.docker.io/v2/stereolabs/iot/manifests/sha256:54f927d254bc6d067a2caedc639eb74039b9fd5f415b7a0d490daf3db8d58baf: read tcp 192.168.0.107:32900->54.227.20.253:443: read: connection reset by peer
[Error] [2023/12/11, 13:16:24] Cannot deploy application. An error occured while executing docker-compose build.
[Info] [2023/12/11, 13:32:00] build for application Edge Body Tracking 0.1.9...
[Build] [2023/12/11, 13:32:13] Building edge_body_tracking_service
[Build] [2023/12/11, 13:32:14] Step 1/15 : ARG BUILD_IMAGE
[Build] [2023/12/11, 13:32:14] Step 2/15 : ARG RUNTIME_IMAGE
[Build] [2023/12/11, 13:32:14] Step 3/15 : FROM ${BUILD_IMAGE} as builder
[Build] [2023/12/11, 13:32:40] ERROR: Service 'edge_body_tracking_service' failed to build: Head https://registry-1.docker.io/v2/stereolabs/iot/manifests/0.73.2-devel-jetson-l4t35.4-zed4.0: Get https://auth.docker.io/token?scope=repository%3Astereolabs%2Fiot%3Apull&service=registry.docker.io: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[Build] [2023/12/11, 13:32:46] Building edge_body_tracking_service
[Build] [2023/12/11, 13:32:47] Step 1/15 : ARG BUILD_IMAGE
[Build] [2023/12/11, 13:32:47] Step 2/15 : ARG RUNTIME_IMAGE
[Build] [2023/12/11, 13:32:47] Step 3/15 : FROM ${BUILD_IMAGE} as builder
[Build] [2023/12/11, 13:33:02] ERROR: Service 'edge_body_tracking_service' failed to build: Get https://registry-1.docker.io/v2/: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
[Build] [2023/12/11, 13:33:08] Building edge_body_tracking_service
[Build] [2023/12/11, 13:33:09] Step 1/15 : ARG BUILD_IMAGE
[Build] [2023/12/11, 13:33:09] Step 2/15 : ARG RUNTIME_IMAGE
[Build] [2023/12/11, 13:33:09] Step 3/15 : FROM ${BUILD_IMAGE} as builder
[Build] [2023/12/11, 13:33:31] ERROR: Service 'edge_body_tracking_service' failed to build: Head https://registry-1.docker.io/v2/stereolabs/iot/manifests/0.73.2-devel-jetson-l4t35.4-zed4.0: Get https://auth.docker.io/token?scope=repository%3Astereolabs%2Fiot%3Apull&service=registry.docker.io: dial tcp [2600:1f18:2148:bc01:571f:e759:a87a:2961]:443: connect: network is unreachable
[Error] [2023/12/11, 13:33:34] Cannot run application. An error occured while executing docker-compose build.
5

Hi @daGoedie,

Sorry to learn that.
From the logs, I would say that the application was not able to pull the Docker image.
You can try to pull the image manually on the Jetson with:

docker pull stereolabs/iot:0.73.2-devel-jetson-l4t35.4-zed4.0

If the pull fails, you should try to pull another Docker image to see if Docker is broken or not.

1 Like