Stanford OpenLDAP in Container
- Stanford OpenLDAP in Container
- Get and setup personal drone token
- Turn on the ci job defined in .drone.yml
- Update ldap image
Stanford OpenLDAP in Container
This repository contains instructions how to build and publish docker-ldap image to Google Container Registry.
This repo supports DroneCI.
Get and setup personal drone token
Drone CLI requires access token to talk to drone server.
Please get your personal token, and save the the token to ${HOME}/.drone-token file.
NOTE: Do not add newline at the end of the token.
Turn on the ci job defined in .drone.yml
NOTE: This will setup the hook for CI trigger. This only needs to be done once. You probably don't need to run this if it's been setup already.
$ make drone-setupSee .drone.yml for build steps and triggers.
Update openldap image
If you make changes to the repository, you can test build manually. If the build is successful, then commit and push changes to the docker-ldap repository. It will trigger CI/CD to build and upload gcr.io/uit-authnz/openldap:latest image.
Manual push to Google container registry
# make build
$ make push
Updating PS cloud framework from Git into /Users/sfeng/bin/ps-cloud-framework...
VAULT SERVER: https://vault.stanford.edu
You are logged in VAULT and have permission to read from secret/projects/uit-authnz/*
Login Succeeded
Push gcr.io/uit-authnz/ldap:048d8295ebbd129086db9161b12b101eb685959e ...
The push refers to repository [gcr.io/uit-authnz/ldap]
e53371689781: Pushed
a8eb0a957605: Pushed
188e99cd395e: Pushed
f819153fc68b: Pushed
d982fc324e3e: Pushed
4276ef46cf43: Pushed
96e57cd3c993: Layer already exists
240b0bdf7f50: Layer already exists
202b974c712a: Layer already exists
43a852aaa685: Layer already exists
latest: digest: sha256:e56efd42b560cffa77a588b0e9ecde71110ec74a6c101d7f53a838a587a460a1 size: 2402