Running object-detector-python example behind a proxy #35
-
|
I’m trying to run object detection example (https://github.com/AxisCommunications/acap-computer-vision-sdk-examples/tree/master/object-detector-python) on a P3265-LV. docker-compose --tlsverify -H tcp://$AXIS_TARGET_IP:$DOCKER_PORT --env-file ./config/env.$ARCH.$CHIP up it displays the following message for 15 seconds and then displays the following error message: This message seem to come from the docker inside the camera, not from the build server. When I ssh to the camera and execute time="2022-06-03T15:28:08.920695739-04:00" level=warning msg="Error getting v2 registry: Get \https://registry-1.docker.io/v2/\: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" Is there a workaround for this issue? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
Hi @igor-rud-kr and welcome! I'll move this discussion into https://github.com/AxisCommunications/acap-computer-vision-sdk-examples. The maintainers will hopefully be able to help you on your way. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Igor If docker can't pull the image from the camera, a quick fix is to upload the runtime-image manually like you do for the other two images: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! The error message that I am getting now is object-detector-python-object-detector-python-1 | standard_init_linux.go:219: exec user process caused: exec format error Can you please point me in the right direction - how can I trace this issue? |
Beta Was this translation helpful? Give feedback.
Hello Igor
If docker can't pull the image from the camera, a quick fix is to upload the runtime-image manually like you do for the other two images:
docker save axisecp/acap-runtime:0.6-aarch64 | docker --tlsverify -H tcp://$AXIS_TARGET_IP:$DOCKER_PORT load