If you are wondering where the data of this site comes from, please visit GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
apopp DoctahPopp871 New York NY Automater of Things.

DoctahPopp871/amplify-js 0

A declarative JavaScript library for application development using cloud services.

DoctahPopp871/aws-alb-ingress-controller 0

AWS ALB Ingress Controller for Kubernetes

DoctahPopp871/aws_puppet_autosign 0

Repository including .rb executable and csr_attributes file to utilize aws metadata during policy based auto cert sign

DoctahPopp871/bower-angular-mocks 0

angular-mocks.js bower repo

DoctahPopp871/cms-kube 0

Kubernetes based Cancer Management System

DoctahPopp871/filebrowser 0

📂 Web File Browser which can be used as a middleware or standalone app.

DoctahPopp871/pTuneos 0

pTuneos: prioritizing Tumor neoantigen from next-generation sequencing data

DoctahPopp871/puppetlabs-aws 0

Puppet module for managing AWS resources to build out infrastructure

DoctahPopp871/ReviewNinja-Welcome 0

Welcome repo for ReviewNinja to help you get started. Feel free to delete when you're done, we won't take it personally.

DoctahPopp871/scout 0

VCF visualization interface

issue commentquay/clair

could not pull ubuntu-cve-tracker repository The requested URL returned error: 503

Hello, I just ran into the same error and opened a similar issue :

Im wondering why the git:// is not being used, it seems to be more stable then the HTTP(s) endpoint.


comment created time in 3 months

issue openedquay/clair

could not pull ubuntu CVE tracker repository using HTTPs URL


Project discussion and other meta topics should be discussed on the mailing list.

GitHub issues are ONLY for bugs and features for the Clair API. Please first create an issue on your client's repository before opening one here.

Are you using a development build of Clair? Your problem might be solved by switching to a stable release.


Description of Problem / Feature Request

<could not pull ubuntu-cve-tracker repository The requested URL returned error: 503>

Expected Outcome

<Event":"finished fetching","Level":"info","Location":"updater.go:253","Time":"2021-04-21 16:15:40.668695","updater name":"ubuntu"}>

Actual Outcome

< clair {"Event":"could not pull ubuntu-cve-tracker repository","Level":"error","Location":"ubuntu.go:174","Time":"2021-06-24 17:45:40.445250","error":"exit status 128","output":"Cloning into '.'...\nfatal: unable to access '': The requested URL returned error: 503\n"} clair {"Event":"an error occured when fetching update","Level":"error","Location":"updater.go:246","Time":"2021-06-24 17:45:40.445324","error":"could not download requested resource","updater name":"ubuntu"}>



  • Clair version/image: 2.1.7
  • Clair client name/version:
  • Host OS: cos-linux
  • Kernel (e.g. uname -a): 5.4.89+ #1 SMP Sat Feb 13 19:45:14 PST 2021 x86_64 Intel(R) Xeon(R) CPU GenuineIntel GNU/Linux
  • Kubernetes version (use kubectl version): not used
  • Network/Firewall setup:

This is related to issue :

I have been able to replicate this connectivity issue locally by interacting with the HTTPs URL via git clone

Cloning into 'ubuntu-cve-tracker'...
fatal: unable to access '': The requested URL returned error: 503

However when using the git based url git:// The tracker succeeds. If the HTTPs URL is unstable server side, and the git url is stable, is there any reason why that is not being used ?

Change could be made here to use the non HTTPs URL :

created time in 3 months