Can NOT get a single camera to work or... #221

mikeoverbay · 2022-03-06T02:39:16Z

mikeoverbay
Mar 6, 2022

I don't know what the address is.
I have 2 containers running. The cam is setup in the first one only but I can not get to it.
I can run the 2 OctoPrint web interfaces and they work with my 2 printers.
The Pi finds the camera fine. I can test it
This is the container code. Sorry it striped the white space alignment from it. I attached a text file of it also.

Docker_Code.txt

version: '3.6'
services:

Octoprint1

octoprint1:
container_name: Octoprint1
image: octoprint/octoprint
hostname: Octoprint1
restart: unless-stopped
ports:
- 5000:5000
- 8080:8080
volumes:
- /home/dietpi/docker/octoprint1:/octoprint1
environment:
- ENABLE_MJPG_STREAMER=true
- MJPG_STREAMER_INPUT=-n -d /dev/video0:/dev/video0 -r 1280x720 -f 30
devices:
#Printer Port
- /dev/ttyACM0:/dev/ttyACM0
#Webcam port
# - /dev/video0:/dev/video0

Octoprint2

octoprint2:
container_name: Octoprint2
image: octoprint/octoprint
hostname: Octoprint2
restart: unless-stopped
ports:
- 5001:5000
- 8081:8080
volumes:
- /home/dietpi/docker/octoprint2:/octoprint2
devices:
- /dev/ttyUSB0:/dev/ttyUSB0

Paraphraser · 2022-03-06T12:08:48Z

Paraphraser
Mar 6, 2022

What happens if you try it like this?

  octoprint1:
    container_name: Octoprint1
    image: octoprint/octoprint
    hostname: Octoprint1
    restart: unless-stopped
    ports:
    - 5000:5000
    - 8080:8080
    volumes:
    - /home/dietpi/docker/octoprint1:/octoprint1
    environment:
    - ENABLE_MJPG_STREAMER=true
    - MJPG_STREAMER_INPUT=-n -r 1280x720 -f 30
    - CAMERA_DEV=/dev/video0
    devices:
    - /dev/ttyACM0:/dev/ttyACM0
    - /dev/video0:/dev/video0

I use:

    - MJPG_STREAMER_INPUT=-r 1152x648 -f 10

I'm not sure what -n does. I tried a few values but settled on 1152x648 as a reasonable "wide-screen" approximation for the Pi ribbon-cable camera. I think 10fps is the default frame-rate. That's the only value I've ever used. At 30fps I'd be a bit worried about the load (encoding, transmission) on the Pi 3B+ I'm using.

I've got some other notes in my docker-compose as follows:

    # Octoprint configuration UI:
    #        Stream URL: /webcam/?action=stream
    #      Snapshot URL: http://localhost:8080/?action=snapshot
    #    Path to FFMPEG: /usr/bin/ffmpeg

Hope this helps.

1 reply

mikeoverbay Mar 6, 2022
Author

Thank you for answering!
Let me give this a try.
So far, I get two good containers but I can not access the camera.

mikeoverbay · 2022-03-06T15:02:47Z

mikeoverbay
Mar 6, 2022
Author

What mode are you running the camera? Should it be in legacy mode?

0 replies

Paraphraser · 2022-03-06T21:20:45Z

Paraphraser
Mar 6, 2022

I'm sorry but I don't really understand your question. I am running Raspbian Buster because, as far as I'm aware, there is as yet no camera support for OctoPrint in Bullseye (or maybe it's FFMPEG that needs updating - I don't know). I think of Buster as the "legacy system" which has camera support for OctoPrint. It might mean the same thing as your question. Sorry to be so vague.

If there's a way of running either (a) Bullseye with Buster-style camera support that then works with FFMPEG and OctoPrint, or (b) OctoPrint on Bullseye such that FFMPEG/OctoPrint can use the native Bullseye camera system, I haven't come across it. I did some searching when Bullseye first became the official release but not since. I'd be interested to hear about any progress.

0 replies

mikeoverbay · 2022-03-07T02:34:53Z

mikeoverbay
Mar 7, 2022
Author

I appreciate the help.
I was just wondering if legacy setting in raspi-config needs enabled. I'm still struggling with this. I think libcamera could be hijacking my camera.
This will launch the built in streamer fine but no image shows up anywhere.
I am going to reinstall everything. All this messing around with config files has probably broke it.
I saved this on my desktop. I should stream according to everything I have read and your help so the issue lies elsewhere.

services:
##### Octoprint1
  octoprint1:
    container_name: Octoprint1
    image: octoprint/octoprint
    hostname: Octoprint1
    restart: unless-stopped
    ports:
      - 5000:5000
      - 8080:8080
    volumes:
      - /home/dietpi/docker/octoprint1:/octoprint1
    environment:
      - ENABLE_MJPG_STREAMER=true
      - MJPG_STREAMER_INPUT=-r 1280x720 -f 30
      - CAMERA_DEV:/dev/video0
    devices:
      #Printer Port
      - /dev/ttyACM0:/dev/ttyACM0
      #Webcam port
      - /dev/video0:/dev/video0
##### Octoprint2
  octoprint2:
    container_name: Octoprint2
    image: octoprint/octoprint
    hostname: Octoprint2
    restart: unless-stopped
    ports:
      - 5001:5000
      - 8081:8080
    volumes:
      - /home/dietpi/docker/octoprint2:/octoprint2
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0


    # Octoprint configuration UI:
    #        Stream URL: /webcam/?action=stream
    #      Snapshot URL: http://localhost:8080/?action=snapshot
    #    Path to FFMPEG: /usr/bin/ffmpeg

0 replies

Paraphraser · 2022-03-07T03:55:26Z

Paraphraser
Mar 7, 2022

That's a possibility. My /boot/config.txt ends with:

# enable raspicam
start_x=1
gpu_mem=128

I think that got there via enabling the camera in raspi-config.

But, right back at the beginning of this post, I thought you said that the camera worked fine. I assumed you meant you'd used something like raspistill -o test.jpg with test.jpg recording whatever the camera was pointing at. I could be wrong but I don't think raspistill works if the camera is not enabled so, if raspistill works then the camera is working and should be available to the container.

Also, I just noticed something else. In this fragment:

    volumes:
    - /home/dietpi/docker/octoprint1:/octoprint1

I think that's wrong. I think it should be:

    volumes:
    - /home/dietpi/docker/octoprint1:/octoprint

and the second container should be:

    volumes:
    - /home/dietpi/docker/octoprint2:/octoprint

What is going on is that the left hand side (before the colon) represents the path outside the container (ie on the Raspberry Pi's file system) while the right hand side is the path inside the container (relative to the container's file system). I think the internal path /octoprint is constructed and populated as part of the container so my guess is /octoprint1 doesn't have any content.

I don't think that necessarily explains the problem with the camera.

Other than that, I don't really know. Sorry.

1 reply

mikeoverbay Mar 10, 2022
Author

I used what the examples showed.
I could get to the camera server via port 8080 so I knew it was working. The containers could not. It could of been the path issue you mentioned.

mikeoverbay · 2022-03-07T06:15:39Z

mikeoverbay
Mar 7, 2022
Author

I got it working with your help! Thank you!
I did a fresh install of Buster and set it up with your info and it all works.
The new OS seems to have some issues with the camera. Not sure but I wasted 4 days. Good thing SDs work in my printers :)

0 replies

danielXengines · 2022-08-03T19:48:28Z

danielXengines
Aug 3, 2022

Hi there,

I would like to ask if anyone managed to get the camera working in octoprint with a raspi running on bullseye?

My pi is running bullseye and octoprint itself works OK
The camera works on the pi. libcamera-still works and I even enabled legacy camera support to test raspistill, which works as well.

Inside the octoprint container though neither libcamera-still nor raspistill work (similar to what mikeoverbay reported)
I also see that the octoprint is on Linux 10 buster.

I would like to stay with bullseye, so if it's possible to get the camera working on bullseye, I would be happy to hear from you. Thank you!!

Kind regards

1 reply

Paraphraser Aug 4, 2022

Yes.

I'm running octoprint/octoprint:latest on a Pi 4 using full 64-bit Bullseye.

This is with a standard Raspberry Pi ribbon camera.

Some time ago I wrote a gist on the topic and I've just made sure it's fully up-to-date.

The main focus of the gist is to explain how to set up UDEV rules so that the OctoPrint service remains available when the printer is switched on and off.

I also wanted the camera to follow the printer (no sense in the camera being on if the printer is switched off) but that's just a bit of extra polish on the basic problem of Bullseye + Camera + OctoPrint.

The gist is actually intended for SensorsIot/IOTstack users so it assumes a few folder and file structures.

I also maintain the PiBuilder repo which is intended to help IOTstack users get a rock-solid foundation for running IOTstack.

One of PiBuilder's options is ENABLE_PI_CAMERA=legacy and that is what you need for OctoPrint to use a standard Raspberry Pi ribbon camera on Bullseye. The ribbon camera is the only camera I have so I really can't say what's needed for other cameras.

Because PiBuilder is intended for IOTstack, it also installs that plus all dependencies as part of the build. In other words, if you're prepared to start from a clean build and are happy to let PiBuilder do the work, you'll wind up with the IOTstack structures assumed by the gist, and it might be easier to make sense of the gist. To be clear, you don't need IOTstack. It's just a means to an end. Once you see how it all hangs together, you can arrange the pieces of the puzzle any way you like.

View of my Pi 4 sitting on top of a tripod:

What the Pi camera sees:

A few system facts:

$ uname -a
Linux sys-bak 5.15.32-v8+ #1538 SMP PREEMPT Thu Mar 31 19:40:39 BST 2022 aarch64 GNU/Linux

$ grep PRETTY_NAME /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"

$ docker image inspect iotstack_octoprint:latest | jq .[0].Architecture
"arm64"

$ docker version
Client: Docker Engine - Community
 Version:           20.10.17
 API version:       1.41
 Go version:        go1.17.11
 Git commit:        100c701
 Built:             Mon Jun  6 23:02:34 2022
 OS/Arch:           linux/arm64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.17
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.17.11
  Git commit:       a89b842
  Built:            Mon Jun  6 23:01:01 2022
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.6
  GitCommit:        10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
 runc:
  Version:          1.1.2
  GitCommit:        v1.1.2-0-ga916309
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ docker-compose version
Docker Compose version v2.6.0

I hope something in this helps you solve your problem.

danielXengines · 2022-08-04T19:47:40Z

danielXengines
Aug 4, 2022

Wow !! Thank you for your reply & the detailed explanation. I do not understand it all as yet, will go thru it this weekend and try to set it up. Will report back soon. Thanks again for your help!!

0 replies

danielXengines · 2022-08-06T14:23:14Z

danielXengines
Aug 6, 2022

Hello Phil,

Thank you for the detailed explanation and the proposed solution. I must confess, I could not fully understand the details of the framework and I decided to experiment with some alternatives instead.

I did find a solution and it involved enabling legacy camera support in raspi-config and adding the following lines of code (for vcgencmd) to the docker-compose.yaml file ... (this i learnt from another post).

volumes: - octoprint:/octoprint - /usr/bin/vcgencmd:/usr/bin/vcgencmd - /usr/lib/arm-linux-gnueabihf/libvcos.so.0:/usr/lib/arm-linux-gnueabihf/libvcos.so.0 - /usr/lib/arm-linux-gnueabihf/libvchiq_arm.so.0:/usr/lib/arm-linux-gnueabihf/libvchiq_arm.so.0

The above code got rid of the vcgencmd warnings I do not know if it's actually required for the camera to function correctly.

octoprint in the docker container is still running on buster and this is not an issue.

Thank you for your help!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Can NOT get a single camera to work or... #221

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 9 comments 3 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

Can NOT get a single camera to work or... #221

Octoprint1

Octoprint2

Replies: 9 comments · 3 replies

mikeoverbay Mar 6, 2022 Author

mikeoverbay Mar 6, 2022 Author

mikeoverbay Mar 7, 2022 Author

mikeoverbay Mar 10, 2022 Author

mikeoverbay Mar 7, 2022 Author

Replies: 9 comments 3 replies

mikeoverbay Mar 6, 2022
Author

mikeoverbay
Mar 6, 2022
Author

mikeoverbay
Mar 7, 2022
Author

mikeoverbay Mar 10, 2022
Author

mikeoverbay
Mar 7, 2022
Author