-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown service clairpb.AncestryService #115
Comments
@apexcz what version of Calr do you use? I have the same issue with the current master, but it works for many others (which is you got via |
@hashmap I use the latest version of Clair - image: quay.io/coreos/clair-git:latest |
@hashmap thank you and please let me know when it is merged. |
@apexcz it was merged and it's why you have this issue:) it's not a part of any release yet, so please try the last release, not master branch |
@hashmap I tried using the latest binary release - Klar 2.3.0 for osx and I still get the same error message as shown below. Failed to analyze using API v3: push image https://registry-1.docker.io/v2/library/postgres:9.5.1 to Clair failed: rpc error: code = Unimplemented desc = unknown service clairpb.AncestryService Failed to analyze, exiting |
@hashmap I am still having the same issues with the latest binary release - Klar 2.3.0 for osx. I have even tried with other release versions down till version 2.0 where the error message changes to Failed to analyze using API v3: push image https://registry-1.docker.io/v2/library/postgres:9.5.1 to Clair failed: rpc error: code = Unavailable desc = all SubConns are in TransientFailure What do you suggest in this case? |
The errors seems to occur because the /v1/layers endpoint is no longer supported. See my trace output after trying to scan the image kinihun/klar from hub.docker.com:
|
@a-zen, I agree with you. I had to use coreos/clair v2.0.4 (the stable release) instead of coreos/clair-git:latest (development release). Delete current version of Clair and modify $HOME/docker-compose.yml file from image: quay.io/coreos/clair-git:latest to |
@apexcz so this is a clair bug and not an klar one? |
@a-zen Yes, because the latest clair-git version doesn't support /v1/layers. Although Klar should fully support v3. |
Not really, |
With the clair-git:latest version clair is up and running but the error when trying with klar is docker run --env-file=env-file.env docker.io/poojatbabu/klar postgres:9.5.1 Failed to analyze using API v3: push image https://registry-1.docker.io/v2/library/postgres:9.5.1 to Clair failed: rpc error: code = Unavailable desc = all SubConns are in TransientFailure when i try with clair:v2.0.7 / clair:v2.0.5 / clair:latest clair is not up and running error says {"Event":"pgsql: could not open database: dial tcp 127.0.0.1:5432: getsockopt: connection refused","Level":"fatal","Location":"main.go:96","Time":"2019-02-10 16:25:57.674339"} where as the postgres:9.6 is up and running fine am i missing something, am trying to set up clair for the first time, help is highly appreciated. |
@hashmap I just installed the latest version of klar - 2.3.0 (as at the time of writing) by the go get github.com/optiopay/klar command. This is the result I get
$ CLAIR_ADDR=localhost CLAIR_OUTPUT=High CLAIR_THRESHOLD=10 klar postgres:9.5.1
clair timeout 1m0s
docker timeout: 1m0s
no whitelist file
Analysing 22 layers
Failed to analyze using API v1: push image https://registry-1.docker.io/v2/library/postgres:9.5.1 to Clair failed: can't even read an error message: invalid character 'N' looking for beginning of value
Failed to analyze using API v3: push image https://registry-1.docker.io/v2/library/postgres:9.5.1 to Clair failed: rpc error: code = Unimplemented desc = unknown service clairpb.AncestryService
Failed to analyze, exiting
$
Meanwhile, my previous version (last week) was working fine with the above command, but I was having issues implementing Klar's Dockerized version so I had to uninstall and re-install klar and clair. Please help me look into this issue.
The text was updated successfully, but these errors were encountered: