Dewey is an application for syncing a list of Docker repositories for registries that don't support v2/_catalog. Based on a list of "orgs", Dewey will generate the same output as v2/_catalog for a subset of the content of the registry. This way, you only include what you care about. Also, you can include a static list of repositories that you wish add in the event that you only want 1 or 2 of the repositories for a given org.
- Dockerhub
- Quay
The default path is at /opt/dewey/config.yaml, then $HOME/.dewey, then .. The format is as follows:
registries:
- name: quay
kind: quay
password: somePassword
orgs:
- skuid
- ethanfrogers
- name: dockerhub
kind: dockerhub
username: someUsername
password: somePassword
repositories:
- gliderlabs/consul-server
orgs:
- selenium
- jenkinsTo use dewey with Spinnaker, it will need to be running as a sidecar of Clouddriver. If you're deploying on Kubernetes, you'll want to run dewey in the same Pod as Clouddriver with a shared emptyDir volume between them. If you're running on EC2, it may be enough to have it running on the same host.
To configure Clouddriver, use the catalogFile option instead of listing repositories when configuring your Docker accounts. Note, this option is not exposed in Halyard at this time.
# Dewey config
registries:
- name: dockerhub
kind: dockerhub
repositories:
- gliderlabs/consul-server
orgs:
- selenium
- jenkins# Clouddriver config
# simple Dockerhub config with no private orgs
dockerRegistry:
enabled: true
accounts:
- name: dockerhub
address: https://index.dockerhub.io
catalogFile: /opt/dewey/catalogs/dockerhub.jsonWith the above configuration, Dewey will output a list of all repositories available for the jenkins and selenium orgs on Dockerhub. If new repositories are ever added, Dewey will pick them up and include them in the list. Clouddriver will use this list each time it caches image tags to make sure it's caching the right repositories.
$ mkdir catalogs
$ docker run --rm -v $(pwd)/catalogs:/opt/dewey/catalogs -v $(pwd)/config.yaml:/opt/dewey/config.yaml dewey:0.0.3Since these registries do not support v2/_catalog, we can't utilize Docker Registrys APIs to get our final result. This means that we need to go through application APIs to get our data.
Credentials for Quay aren't the same as your docker login credentials. For Quay, you will need to generate a Token for an "Application".
The API address for your service can differ from registry to registry. Dockerhub, for example, lists it's application API at https://hub.docker.com. Quay's is listed at https://quay.io. If you are using a registry hosted by some other provider, the address option is overridable.
$ ./dewey --help
Usage of ./dewey:
--dir string catalog file output directory (default "/opt/dewey/catalogs")
--interval string sync interval (default "30s")
--pretty pretty print output