Glad you got things working! Thanks for the patience Suresh and help Jimmy.

On Thu, Aug 11, 2016 at 12:13 PM Suresh Ramamurthy <[email protected]>
wrote:

> Hi Jimmy,
>
> Thanks for helping me out.
>
> I stopped the containers and re-ran the docker-compose command to start
> the containers. Now, I am able to access the APIs as u mentioned and
> get the information
>
> thanks
> Suresh
>
>
> On Wednesday, August 10, 2016 at 6:15:41 PM UTC-7, Jimmy Zelinskie wrote:
>>
>> The health endpoint is actually localhost:6061/health
>>
>> Sorry about that.
>>
>> On Wednesday, August 10, 2016 at 9:14:09 PM UTC-4, Jimmy Zelinskie wrote:
>>>
>>> Hi Suresh,
>>>
>>> The 404 is unlikely to be an error. Clair does not have a root HTTP
>>> route as its API is versioned.
>>> Try hitting port 6061 which should return the health status or attempt
>>> to hit a route documented here[0] with a "localhost:6060/v1" prefix.
>>>
>>> [0]: https://github.com/coreos/clair/tree/master/api/v1
>>>
>>> I hope this helps,
>>> Jimmy
>>>
>>> On Wednesday, August 10, 2016 at 6:57:26 PM UTC-4, Suresh Ramamurthy
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I am new to Clair and I need some help in setting up Clair.
>>>>
>>>> I followed the instructions to install Clair using Docker Compose
>>>> approach from below link:
>>>>
>>>> https://github.com/coreos/clair
>>>>
>>>> Both, clair and postgres containers are up. But, when I connect to
>>>> Clair using localhost:6060 I get *404 page not found*
>>>>
>>>> To debug this issue, I looked into the Clair logs using "docker logs
>>>> <clair container ID>" and I found below error:
>>>>
>>>> pgsql: insertVulnerabilityFixedInFeature: pq: duplicate key value
>>>> violates unique constraint
>>>> "vulnerability_fixedin_feature_vulnerability_id_feature_id_key"
>>>>
>>>>
>>>> When I logged into postgres container, I found that the tables were
>>>> filled with vulnerability information.
>>>>
>>>> Could some one shed some light on this issue and help me resolve the
>>>> problem?
>>>>
>>>> Please find the clair log file in the attachment that contains the
>>>> error messages.
>>>>
>>>> thanks
>>>> Suresh
>>>>
>>>>
>>>>

Reply via email to