How to run this locally and try it out?

[okainov]

I find the documentation quite confusing tbh... I just want to start it locally, try it out and see how it works (and whether it works).

docker compose up -d works fine and I see Traefik dashboard. But that's where it starts to be unclear.

localhost:6060
Clair services.

How can I check it's working? Going in browser gives me "404 page not found"

Quay (if started)

Do I need to start it? What does it do? How do I ensure it's started (if needed)? This all is missing completely in the documentation.

Seems like this is required, because the very next step says "Pushing to the Local Quay" - but it's not running with the default configuration.. And even if I do docker compose --profile quay up -d and try the suggested command line, I get 502 or 504 (and Quay is still not accessible via browser on whatever port, it's not even clear how to figure out "random" port. In the logs I see prometheus-related errors like failed to push registry to pushgateway at http://localhost:9091)

I found this issue #2098 and especially this comment quite useful as it gives the "magical command line" which seems to be what I actually need: go run ./cmd/clairctl -config ./local-dev/clair/config.yaml -D report -host http://localhost:6060 docker.io/docker/dockerfile:1.7. However it gives me error:

go run ./cmd/clairctl -config ./local-dev/clair/config.yaml -D report -host http://localhost:6060 docker.io/docker/dockerfile:1.7
2025-12-12T06:12:32-08:00 DBG enabling signing for authorities authorities=["webhook-target","clair-indexer:6060","clair-matcher:6060"]
2025-12-12T06:12:32-08:00 DBG fetching ref=docker.io/docker/dockerfile:1.7
2025-12-12T06:12:32-08:00 DBG using text output
2025-12-12T06:12:34-08:00 DBG found manifest digest=sha256:b5f3b260a9678e1d83d2fce86eeddf79420b79147eaba2a25986f47133d73720 ref=docker.io/docker/dockerfile:1.7
2025-12-12T06:12:34-08:00 DBG requesting index_report attempt=1 digest=sha256:b5f3b260a9678e1d83d2fce86eeddf79420b79147eaba2a25986f47133d73720 ref=docker.io/docker/dockerfile:1.7
2025-12-12T06:12:34-08:00 DBG body="no available server\n" digest=sha256:b5f3b260a9678e1d83d2fce86eeddf79420b79147eaba2a25986f47133d73720 method=GET path=/indexer/api/v1/index_report/sha256:b5f3b260a9678e1d83d2fce86eeddf79420b79147eaba2a25986f47133d73720 ref=docker.io/docker/dockerfile:1.7 status="503 Service Unavailable"
2025-12-12T06:12:34-08:00 DBG index error error="unexpected return status: 503" digest=sha256:b5f3b260a9678e1d83d2fce86eeddf79420b79147eaba2a25986f47133d73720 ref=docker.io/docker/dockerfile:1.7
2025-12-12T06:12:34-08:00 ERR error="unexpected return status: 503"

Any ideas how can one actually try it? And also I'd appreciate updating documentation for getting started...

Just in case, I'm running it in corporate environment behind proxy, but all the env variables should be properly set, so I don't think it's the issue...

[crozzy]

Hi, the local-dev setup can be run with a number of different profiles (as you have seen), the default profile does not include quay (and quay is not needed to verify functionality). The address to reach quay should be printed if using the make command. I will add a note to go through the local workflow and update the docs.

As to the actual error; it looks like the proxy that is being used is not allowing clair to pull down the relevant layers from docker hub, I'm guessing either an exception needs to be added or images need to hosted within the same network boundary.