Use this action to sign in a local container configuration file to an Open Container Initiative (OCI) registry, such as Docker Hub, with a username and password.
Prerequisites
Make sure to add the following to your YAML file:
- name: Check out repo uses: actions/checkout@v1
All CloudBees action repositories are listed at CloudBees, Inc. on GitHub. |
Inputs
Input name | Data type | Required? | Description |
---|---|---|---|
|
String |
Yes |
The registry server URL. |
|
String |
Yes |
The registry username. |
|
String |
Yes |
The registry password. |
Usage examples
Sign in to registry, build and push a container image
Sign in to an OCI registry, then build, tag, and push a container image to it.
- name: Sign in to OCI registry uses: cloudbees-io/configure-oci-credentials@v1 with: registry: ${{ vars.OCI_REGISTRY }} username: ${{ secrets.OCI_USERNAME }} password: ${{ secrets.OCI_PASSWORD }} - name: Build, tag, and push container image to OCI registry uses: cloudbees-io/kaniko@v1 with: destination: ${{ vars.OCI_REGISTRY }}/my-oci-repo:latest
For more information, refer to CloudBees action: Build and publish Docker images with Kaniko.
Sign in to registry, package and push a Helm chart
Sign in to an OCI registry, then package and push a Helm chart to it.
- name: Sign in to OCI registry uses: cloudbees-io/configure-oci-credentials@v1 with: registry: ${{ vars.OCI_REGISTRY }} username: ${{ secrets.OCI_USERNAME }} password: ${{ secrets.OCI_PASSWORD }} - name: Package and push Helm chart to OCI registry uses: docker://alpine/helm:latest run: | helm package my-oci-repo helm push my-oci-repo-0.1.0.tgz ${{ vars.OCI_REGISTRY }}
(For Kaniko users) Helm and Kaniko use the same credential store, so you can use the same credentials for both. |