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
Thats a lot of pulls. But it looks like there was only one push, 5 months ago.
Does anyone have an idea who all those pulls are from? It would be good to know as it could help direct future image releases.
In the past I had a personal docker image on dockerhub that I made public and got a similar amout of pulls even though I was the only user. Turned out it was part of my continuous deploy system that was regularly checking dockerhub for image updates. The check ran 'docker pull', but even if the local copy never changed it was added to the pull count. Is there anything known about in the cypht infrastructure (or perhaps the related tikiwiki project) that may be doing this?
The text was updated successfully, but these errors were encountered:
If there are no way to get insights on the dockerhub account about specific usage, perhaps there is a way through the packageist account?
I mention this because if you see here, Cypht has the most downloads, while roundcube has a lot more start. Which also is an indication something unusual is going on.
In 2017, I suggested that Roundcube be made available on Packagist.org. At the time, it was not a priority for the project leaders: roundcube/roundcubemail#5938
I made the same suggestion for Cypht in 2019: #311 (comment)
It was implemented and Cypht got over 80 000 downloads :-)
It looks like Roundcube very recently changed their mind, which is why there are only 103 downloads. Given how popular Roundcube is, I expect that figure will grow quickly.
馃挰 Question
Dockerhub reports 100k+ pulls from here:
https://hub.docker.com/r/sailfrog/cypht-docker
Thats a lot of pulls. But it looks like there was only one push, 5 months ago.
Does anyone have an idea who all those pulls are from? It would be good to know as it could help direct future image releases.
In the past I had a personal docker image on dockerhub that I made public and got a similar amout of pulls even though I was the only user. Turned out it was part of my continuous deploy system that was regularly checking dockerhub for image updates. The check ran 'docker pull', but even if the local copy never changed it was added to the pull count. Is there anything known about in the cypht infrastructure (or perhaps the related tikiwiki project) that may be doing this?
The text was updated successfully, but these errors were encountered: