mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
Docker image and Raspberry Pi 500 #2681
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#2681
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ilkkamr26 on GitHub (Feb 13, 2026).
Hi!
https://hub.docker.com/search?q=motioneye&sort=updated_at&order=desc
There are 158 images of MotionEye in Docker Hub. How could you become a Verified Publisher?
https://hub.docker.com/r/motioneyeproject/motioneye
Could you make a Docker image for arm64 systems like Raspberry Pi 500?
https://github.com/motioneye-project/motioneye/blob/main/docker/README.md
This README.md is pretty old. Could you update it?
@MichaIng commented on GitHub (Feb 13, 2026):
Especially, the https://hub.docker.com/r/dontobi/motioneye.rpi image is violating our GPLv3 license, provided with MIT licence which does not require to keep the licence downstream anymore. It would at least need to mention that, while their own Dockerfile can be MIT, the contained motionEye software is GPLv3.
Good question. I created the Docker Hub orga from scratch without deeper knowledge. I will check whether/what the ways are to get a sign that our image is the one generated and uploaded from our repo, i.e. as official as it gets. In info is welcome.
Is is there already: amd64, arm64, armv7, riscv64
#3248
@MichaIng commented on GitHub (Feb 13, 2026):
Seems the Verified Publisher Program is for commercial publishers. Not sure whether it works without being a formal organisation:
But I can try. Would be great if there was a simpler approach, which just implies that images are generated with Dockerfiles and uploaded from workflows from the same repo owner/orga than the contained software it claims to distribute. All those infrastructure and lifted limit perks are not interesting for us, but the only point would be to show Docker users which images are the original/official ones provided by the motionEye maintainers themselves. Some authenticity batch, nothing else.
And another question is whether this is free of costs (which I doubt) 😅.
@ilkkamr26 commented on GitHub (Feb 13, 2026):
Hi!
Could you check what are the requirements for title "Sponsored OSS"?
"Docker-Sponsored Open Source Software. These are images published and maintained by open-source projects that are sponsored by Docker through our open source program."
@MichaIng commented on GitHub (Feb 13, 2026):
Ah right, I forgot about the Sponsored OSS program, checked it here #3226
https://www.docker.com/community/open-source/application/
If that is shown on the image page, it might add some trust/authenticity impression already, though it strictly seen does not give hint about whether the publishers are the true motionEye maintainers.
@MichaIng commented on GitHub (Feb 13, 2026):
I just applied for the Sponsored OSS program, answer within 2 weeks, let's see.