Skip to content

Latest commit

 

History

History
57 lines (38 loc) · 2.19 KB

docker.md

File metadata and controls

57 lines (38 loc) · 2.19 KB

Docker Overview

We use docker to track, test, and deploy our builds.

Tagging Strategy

Images tagged with commit-X (where X is the first 10 characters of a commit hash) refer to a development build against a specific git commit.

These build images, when attached to a pull request, will also be tagged with pull-request-X, where X is the PR number assigned by github. This will always reflect the latest build of the pull request; previous builds will still be accessible by their commit tag above.

Images tagged with deploy-dev.X (where X is an autogenerated, sortable timestamp and version number)

are images that were tagged for deployment to our development environment.

Images tagged with a deploy-eval.X will be automatically deployed to our eval environment.

Prod is the same, but deploy-prod.X

Image Retention

This is a problem that still needs solving. See IAM-258.

GCR Image Repository

The repository for this service is gcr.io/uwit-mci-iam/husky-directory. Access to this repository requires operator permissions on our google project. Team members can reach out on slack for access if they do not have it already.

Github Actions access to gcr.io:

If the security token for Github Actions ever needs to be updated:

  1. Create a new key for the uw-directory-github-actions service account. Download the key.
  2. Base64 encode it. (cat $KEY_FILE_NAME | base64)
  3. Update the GCR_TOKEN secret in the github repository secrets with the base64-encoded value.

This can only be done by a person who is an administrator of this repository, and has access to the project IAM configuration.

Running images

See Running the app.