chirangaalwis
commented
5 years ago I am encountering the Event with the message layer content has already been processed in the past with older engine. skipping analysis quite often.
I would be grateful if someone could explain possible reasons behind this Event.
Demonstrably, I have clair and clairctl working.
I am able to pull/push/analyse images from dockerhub. Running clairctl to analyse , say, tomcat from dockerhub works as expected.
I have local registry instance setup (secure, namely quay enterprise [trial]), and can push images to this repository, and they are successfully analysed by Clair.
However, I cannot figure out how to get a html report from quay, so I thought i would use clairctl to grab an html report.. no such luck.
When I try to analyse the image, I see in the clair logs the following;
{"Event":"processing layer","Level":"debug","Location":"worker.go:73","Time":"2017-08-06 14:38:51.287395","engine version":3,"format":"Docker","layer":"sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4","parent layer":"sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4","path":"https://quay.mt/v2/admin/testimage/blobs/sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4"} {"Event":"layer content has already been processed in the past with older engine. skipping analysis","Level":"debug","Location":"worker.go:101","Time":"2017-08-06 14:38:51.288741","current engine version":3,"layer":"sha256:a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4","past engine version":3}
Any ideas why? I am running the clair container with --insecure-tls ('cos try as I might, I cannot get it to trust the self-signed cert.. not an issue for me at the moment)
Sorry if this is NOT a clairctl issue..