motioneyeos
motioneyeos copied to clipboard
Docker image?
Don't you guys provide docker images like for the old motioneye?
ccrisan/motioneye master-armhf 611591554283 2 years ago 318MB
If so why not?
Their (motionEye Devs) priority currently is to get rid of the Python2.7 code, bringing it up to Python3.x, then the rest of the projects will be easy to build off of it. If you want, though, you can take their current state of motionEye 0.43.0 using the roll your own instructions modify as needed... Docker BTW, for the most part, I place blame on the Python people, as there is no good conversion from 2.7 to 3.0 or 3.1, and even between the 3.x to 3.y versions. It's like they didn't care, and if they didn't like a function, they simply left it out of a newer version...
The latest docker build of the development version of motionEye can be found here. The old prebuilt docker images can be found here.
It is SAD, I was looking around on dockerhub:
https://hub.docker.com/search?q=motioneye&sort=updated_at&order=desc&operating_system=linux&architecture=arm
Pretty much the same versions as my current one:
motionEye Version 0.42.1 Motion Version 4.2.2
No to mention it is always questionable using and trusting others docker images these days and letting a can of worms into your network....
I'm dealing with the same issue (Green screen or no screen) with the Pi Zero and recent motion version + Motioneye:
https://github.com/motioneye-project/motioneye/issues/1136
According to this thread: "EDIT: Solved by enabling fast camera in expert settings." this solves it however does 0.43 has this settings?
If not building that image would be pure waste of time for me.
Thanks.
@mallory98e There is a very complete set of instructions under Build in Docker that has 3 levels of DIY, all of which I checked personally, especially Option 2&3 It is not set up for 0.43.x but works well if you want to mod other options, like motion 4.3.2 or whatever...