Docker image and Raspberry Pi 500 #2681

Open
opened 2026-02-28 01:17:26 -05:00 by deekerman · 5 comments
Owner

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?

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?
Author
Owner

@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.

How could you become a Verified Publisher?

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.

Could you make a Docker image for arm64 systems like Raspberry Pi 500?

Is is there already: amd64, arm64, armv7, riscv64

This README.md is pretty old. Could you update it?

#3248

@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. > How could you become a Verified Publisher? 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. > Could you make a Docker image for arm64 systems like Raspberry Pi 500? Is is there already: amd64, arm64, armv7, riscv64 > This README.md is pretty old. Could you update it? #3248
Author
Owner

@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) 😅.

@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: - https://docs.docker.com/docker-hub/repos/manage/trusted-content/dvp-program/ - https://www.docker.com/partners/programs/ 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) 😅.
Author
Owner

@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."

@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."
Author
Owner

@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): 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.
Author
Owner

@MichaIng commented on GitHub (Feb 13, 2026):

I just applied for the Sponsored OSS program, answer within 2 weeks, let's see.

@MichaIng commented on GitHub (Feb 13, 2026): I just applied for the Sponsored OSS program, answer within 2 weeks, let's see.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/motioneye#2681
No description provided.