GitHub Action to push a container image to an image registry.
Find a file
Tim Etchells 2d063fde99 Add digestfile argument, input, and output
Signed-off-by: Tim Etchells <tetchell@redhat.com>
2021-01-08 17:38:46 +05:30
.github/workflows Add digestfile argument, input, and output 2021-01-08 17:38:46 +05:30
dist Add digestfile argument, input, and output 2021-01-08 17:38:46 +05:30
src Add digestfile argument, input, and output 2021-01-08 17:38:46 +05:30
.gitignore first implementation push to quay action 2020-11-07 13:04:04 +01:00
action.yml Update action.yml 2020-11-28 00:23:19 +05:30
LICENSE first implementation push to quay action 2020-11-07 13:04:04 +01:00
package-lock.json Add verify bundle action and make inputs 'required' 2020-11-17 14:19:07 -05:00
package.json Add verify bundle action and make inputs 'required' 2020-11-17 14:19:07 -05:00
README.md Add digestfile argument, input, and output 2021-01-08 17:38:46 +05:30
tsconfig.json first implementation push to quay action 2020-11-07 13:04:04 +01:00

push-to-registry

Verify Bundle tag badge license badge size badge

Push-to-registry is a GitHub Action for pushing a container image to an image registry, such as Dockerhub, Quay.io, the GitHub Container Registry, or an OpenShift integrated registry.

This action only runs on Linux, as it uses podman to perform the push. GitHub's Ubuntu action runners come with Podman preinstalled. If you are not using those runners, you must first install Podman.

Action Inputs

Refer to the podman push documentation for more information.

Input Required Description
image Yes Name of the image you want to push.
tag No Image tag to push.
Defaults to latest.
registry Yes URL of the registry to push the image to.
Eg. quay.io/<username>
username Yes Username with which to authenticate to the registry.
password Yes Password, encrypted password, or access token with which to authenticate to the registry.
tls-verify No Verify TLS certificates when contacting the registry. Set to "false" to skip certificate verification.
digestfile No After copying the image, write the digest of the resulting image to the file. By default, the filename will be determined from the image and tag. The contents of this file are the digest output.

Action Outputs

registry-path: The registry path to which the image was pushed.
For example, quay.io/username/spring-image:v1.

digest: The pushed image digest, as written to the digestfile.
For example, sha256:66ce924069ec4181725d15aa27f34afbaf082f434f448dc07a42daa3305cdab3.

Examples

The example below shows how the push-to-registry action can be used to push an image created by the buildah-build action.

name: Build and Push Image
on: [push]

jobs:
  build:
    name: Build and push image
    runs-on: ubuntu-latest
    env:
      IMAGE_NAME: my-app
      IMAGE_TAG: latest

    steps:
    - uses: actions/checkout@v2

    - name: Build Image
      uses: redhat-actions/buildah-build@v1
      with:
        image: ${{ env.IMAGE_NAME }}
        tag: ${{ env.TAG }}
        dockerfiles: |
          ./Dockerfile

    - name: Push To Quay
      id: push-to-quay
      uses: redhat-actions/push-to-registry@v1
      with:
        image: ${{ env.IMAGE_NAME }}
        tag: ${{ env.TAG }}
        registry: ${{ secrets.QUAY_REPO }}
        username: ${{ secrets.QUAY_USERNAME }}
        password: ${{ secrets.QUAY_TOKEN }}

    - name: Use the image
      run: echo "New image has been pushed to ${{ steps.push-to-quay.outputs.registry-path }}"

Troubleshooting

Note that quay.io repositories are private by default.

This means that if you push an image for the first time, you will have to authenticate before pulling it, or go to the repository's settings and change its visibility.

Contributing

This is an open source project open to anyone. This project welcomes contributions and suggestions!

Feedback & Questions

If you discover an issue please file a bug in GitHub issues and we will fix it as soon as possible.

License

MIT, See LICENSE for more information.