Closed seanlutner closed 8 years ago
Thanks for your report. Klar tries to follow docker images
output convention for image naming to make UX better. Which means:
my_team/centos7
considered as an image in Docker public registry, translated to the full name registry-1.docker.io/my_team/centos7:latest
centos7
considered as an official image in Docker public registry, translated to the full name registry-1.docker.io/library/centos7:latest
For those cases Klar expects docker credentials to be set it's why you get Can't pull image: Token request returned 401
registry.domain.com/my_team/centos7
is considered as an image my_team/centos7
in private registry registry.domain.com
. Unfortunately only HTTPS (port 443) is supported at the moment, it's why you got a strange error when you specified the port 31832
. I'm going to add this functionality.Please try a new version (v 1.1)
Awesome, that worked! Thanks for the super fast turn around. On additional question. Is Klar doing the docker pull on the image or is that passed off to Clair? My registry uses an internally signed SSL certificate, so I'm wondering where I need to add that as trusted.
Cool. Klar retrieves only metadata via HTTPS and send it to Clair which pulls layer by layer, so technically both components make requests to the registry.
I'll start by saying that I'm not sure if this is an issue with Klar or with Clair itself. I've setup two different instances of Klar and Clair (local on my laptop and on a remote system) and I am seeing errors when trying to scan any Docker images.