Skip to content
This repository has been archived by the owner on Sep 20, 2022. It is now read-only.

Organization data started failing on June 21st around 11:07 GMT #13

Open
thefinn93 opened this issue Jun 23, 2022 · 9 comments
Open

Organization data started failing on June 21st around 11:07 GMT #13

thefinn93 opened this issue Jun 23, 2022 · 9 comments

Comments

@thefinn93
Copy link

Hey there, thanks for this handy tool! According to my prometheus, all my docker_hub_image_pulls_total metrics dropped off a few days ago. I did reviewed the README and did a few tests, and it seems like explicitly specifying images produces the metric, but organizations don't get picked up. I assume this is because docker hub changed something. I haven't had time to look into this, might be something super trivial, but I tested on my laptop with the example command in the README and confirmed this behavior.

@artemkaxboy
Copy link

It's fixed in #14

@artemkaxboy
Copy link

The project looks a bit outdated I wasn't be able to build it. It would be really good if maintainers could accept PR #14 and build new version. Meanwhile I took the core of the service and wrapped it with modern tools golang:1.18, go modules and alpine:3.16.0 it uses a slightly different envs and options and of course new tag namespace instead of user.

I'm going to make a branch in own repo to make fully compatible version for thouse who don't want change a lot prometheus/grafana settings. If the authors don't mind.

@travisghansen
Copy link

Hit the same issue. If you have an image built somewhere let me know and I'll give it a test run.

@artemkaxboy
Copy link

@travisghansen

Check it out artemkaxboy/docker-hub-exporter

Please, make sure you do not pass multiple values in one command option if you use command options for namespaces/images.

DON'T

--namespace="artemkaxboy,nginx"
--image="infinityworks/docker-hub-exporter,infinityworks/build-tools"

DO

--namespace="artemkaxboy" --namespace="nginx"
--image="infinityworks/docker-hub-exporter" --image="infinityworks/build-tools"

And I'm still working on fully compatible version

@travisghansen
Copy link

Still possible to do multiple namespaces using env var?

@artemkaxboy
Copy link

Still possible to do multiple namespaces using env var?

Yes, for envs you use plural noun and a comma to divide:

--env IMAGES="infinityworks/docker-hub-exporter,infinityworks/build-tools"
--env NAMESPACES="artemkaxboy,nginx"

@artemkaxboy
Copy link

artemkaxboy commented Jun 26, 2022

I've finally prepared a fully compatible docker image which can be used for super easy migration. Feel free to use it: artemkaxboy/docker-hub-exporter:legacy

@travisghansen
Copy link

Looks like everything is working perfectly without any changes using your legacy tag. Thanks!

@artemkaxboy
Copy link

Looks like everything is working perfectly without any changes using your legacy tag. Thanks!

Thanks for testing!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants