You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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) 😅.
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."
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.
All three points are done now: the Docker Hub organisation is part of Docker's Sponsored Open Source program, the images are multi-arch including arm64 (also latest/0.44.0: amd64, arm64, armv7, riscv64), so they run on 64-bit Raspberry Pi OS, e.g. on a Pi 500, and docker/README.md was updated in #3484 and #3489 and is linked from the main README since #3488. Closing as completed.
Activity
MichaIng commentedon 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 commentedon 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 commentedon 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 commentedon 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 commentedon Feb 13, 2026
I just applied for the Sponsored OSS program, answer within 2 weeks, let's see.
JamBalaya56562 commentedon Oct 31, 2026
All three points are done now: the Docker Hub organisation is part of Docker's Sponsored Open Source program, the images are multi-arch including arm64 (also
latest/0.44.0: amd64, arm64, armv7, riscv64), so they run on 64-bit Raspberry Pi OS, e.g. on a Pi 500, anddocker/README.mdwas updated in #3484 and #3489 and is linked from the main README since #3488. Closing as completed.triage: motioneye-project#3269 and motioneye-project#1156 closed
MichaIng commentedon Oct 31, 2026
ppc64le and s390x have been added, too.