-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot access camera via gstreamer nvarguscamerasrc in docker container. #1518
Comments
Also I am running into an error when adding the
This seemed similiar to this thread, but should be fixed in our version of nvidia-container-toolkit. Is it possible that this is related to |
Have you tried this with the latest changes on kirkstone? There were some fixes for the container toolkit support that went in at the end of April that eliminated the need to use 'legacy' mode. |
I retried it using commit |
Now I tried it again using the latest commit |
I'm having the same problem when trying to access the Raspberry PI v2.1 camera inside a docker container. My container:
Error seen in the terminal:
|
Do you see anything in nvargus-daemon logs? Based on https://forums.developer.nvidia.com/t/resolving-video-capture-error-in-docker-container-after-restarting-nvargus-daemon/271196/3 you may want to try volume mounting If that doesn't work I'd probably install the equivalent Jetpack image and prove docker works there with the same hardware, use this to compare with your setup. |
I am trying to access an imx477 camera connected via csi to a jetson xavier nx using the devkit board. I built the meta-tegra-demo on branch kirkstone using the base image and the following packages:
I am able to record a test video on the host system using:
Then I launched the container using:
I tried the test video command and this simplified test:
gst-launch-1.0 -e nvarguscamerasrc sensor-id=0 ! fakesink
.Both result in the following error:
I looked at the nvargus-daemon logs in the host system, but could not find any errors besides those also shown when running the command in the host system successfully.
Am I missing something?
The text was updated successfully, but these errors were encountered: