Docker container with camera-streamer about octoprint-docker

[rosenstand]

I would like to try it out too. Maybe I can help. I don't have a ton of docker experience I have done a lot of Linux distro packaging in the past.

I do wonder if it would be cleaner to implement camera-streamer as a separate service/container and then users could choose to compose it together with the current octoprint image. This way there won't be 2 different octoprint images to build and maintain (like OctoPi) and it would be easy to switch between mjpg-streamer and camera-streamer (or you could even use both with different cameras). It would also make it easy to manage multiple cameras and to resource limit the camera container to avoid hugging resources from octoprint (especially nice on multi-instance octoprint setups).

[idaband]

I would like to try it out too. Maybe I can help. I don't have a ton of docker experience I have done a lot of Linux distro packaging in the past.

I do wonder if it would be cleaner to implement camera-streamer as a separate service/container and then users could choose to compose it together with the current octoprint image. This way there won't be 2 different octoprint images to build and maintain (like OctoPi) and it would be easy to switch between mjpg-streamer and camera-streamer (or you could even use both with different cameras). It would also make it easy to manage multiple cameras and to resource limit the camera container to avoid hugging resources from octoprint (especially nice on multi-instance octoprint setups).

i like that idea ...i did install it directly onto the pi (the newer version) I felt it might run better directly on the host. However, I now think wish I would have done it in a separate service.

[barrelltitor]

This is required now for Raspberry pi installs newer than February as only libcamera works due to the removal of the video memory setting from the boot file