Axis Communications
Connection Issues with Docker Daemon on AXIS P3268-LVE Camera #606
-
|
We are using the AXIS P3268-LVE for our project, aiming to test the machine learning capabilities of the camera. We installed and started the Docker Daemon (Docker_Daemon_1_5_0_aarch64_signed.eap) via the camera's admin web page. Additionally, we have generated the necessary certificates for both the host and the client. However, when we execute the command: We receive the following error: Following this, we tried to connect using: Despite the Docker Daemon being reported as running on the admin page, we cannot access it from the client. What could be causing this issue?" |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 17 replies
-
|
This automatically generated reply acts as a friendly reminder. Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them. If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ouaburst , |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ouaburst , Not so sure on the error (# Error: Error -1 getting param in group 'root.DockerdWrapper.Status') 😞 |
Beta Was this translation helpful? Give feedback.
-
|
I have installed the new version of Docker Daemon and started it.
|
Beta Was this translation helpful? Give feedback.
-
|
Please paste your logs from "https://IP/axis-cgi/admin/systemlog.cgi?appname=dockerdwrapper"
This is what worked for me previously. openssl genrsa -aes256 -out ca-key.pem 4096
openssl req -new -x509 -days 365 -key ca-key.pem -sha256 -out ca.pem
openssl genrsa -out server-key.pem 4096
openssl req -subj "/CN=axis-b8a44fXXXXXX" -sha256 -new -key server-key.pem -out server.csr
echo subjectAltName = DNS:axis-b8a44fXXXXXX,IP:192.168.55.237,IP:172.28.160.1,IP:192.168.55.191,IP:172.30.0.1,IP:127.0.0.1 >> extfile.cnf
echo extendedKeyUsage = serverAuth >> extfile.cnf
openssl x509 -req -days 365 -sha256 -in server.csr -CA ca.pem -CAkey ca-key.pem -CAcreateserial -out server-cert.pem -extfile extfile.cnf
openssl genrsa -out key.pem 4096
openssl req -subj '/CN=172.28.160.1' -new -key key.pem -out client.csr
echo extendedKeyUsage = clientAuth > extfile-client.cnf
openssl x509 -req -days 365 -sha256 -in client.csr -CA ca.pem -CAkey ca-key.pem -CAcreateserial -out cert.pem -extfile extfile-client.cnf
scp ca.pem server-cert.pem server-key.pem [email protected]:/usr/local/packages/dockerdwrapper/
exit
Start the ACAP from "https://IP/camera/index.html#/apps"
docker --tlsverify --tlscacert=ca.pem --tlscert=cert.pem --tlskey=key.pem --host=192.168.55.237:2376 version
|
Beta Was this translation helpful? Give feedback.
-
|
OK, it seems that we have problem with the certificate after all. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ouaburst ,
Note: Docker_Daemon_2_0_0_armv7hf_d5880fe_signed.eap used for testing. |
Beta Was this translation helpful? Give feedback.
-
|
Make sure you have TF card and set "SD card Support" to Yes,
|
Beta Was this translation helpful? Give feedback.
-
|
Install the image Run the container The log |
Beta Was this translation helpful? Give feedback.
-
|
Failing due to write /usr/lib/python3.8/test/pycache/test_xml_etree_c.cpython-38.pyc: no space left on device, try after "docker --tlsverify --host tcp://$DEVICE_IP:$DOCKER_PORT compose --env-file ./config/env.$ARCH.$CHIP down --volumes" |
Beta Was this translation helpful? Give feedback.
-
|
I am following the tutorial provided on this GitHub page: However, I am encountering issues in the section titled Install the image. Here is the command I ran and the error message I received: Despite configuring Docker Daemon to utilize the SD card, it seems like I'm still running into a 'no space left on device' error. Could it be that the SD card isn't resolving this issue? I also attempted to run the container with the following command: This resulted in an access denial error suggesting the repository might not exist or may require a 'docker login'. What could be the solution for this? |
Beta Was this translation helpful? Give feedback.
-
|
I don't think "docker login" is the issue here. You can always login again and access arm64v8/ubuntu:22.04.
If I am in your place I will do the following:
|
Beta Was this translation helpful? Give feedback.
-
|
Of course, it slipped my mind to format the SD card! |
Beta Was this translation helpful? Give feedback.
-
|
Use Axis branded SD card or at least Sandisk TF card for Surveillance |
Beta Was this translation helpful? Give feedback.
I don't think "docker login" is the issue here. You can always login again and access arm64v8/ubuntu:22.04.
If I am in your place I will do the following: