GitHub Action to log into a container image registry. For use with podman, buildah, and skopeo.
Find a file
Tim Etchells 9c8a5ab6f3 Update readme
Signed-off-by: Tim Etchells <tetchel@gmail.com>
2021-04-07 12:55:36 -04:00
.github/workflows Modify action.yml 2021-03-31 23:59:17 +05:30
dist Add README.md 2021-04-01 14:08:52 +05:30
git-hooks First commit 🚀 2021-03-30 18:57:12 +05:30
src Add README.md 2021-04-01 14:08:52 +05:30
.eslintrc.js First commit 🚀 2021-03-30 18:57:12 +05:30
.gitignore First commit 🚀 2021-03-30 18:57:12 +05:30
action.yml Modify action.yml 2021-03-31 23:59:17 +05:30
LICENSE First commit 🚀 2021-03-30 18:57:12 +05:30
package-lock.json First commit 🚀 2021-03-30 18:57:12 +05:30
package.json Update code 2021-03-31 14:44:20 +05:30
README.md Update readme 2021-04-07 12:55:36 -04:00
tsconfig.json First commit 🚀 2021-03-30 18:57:12 +05:30

buildah-build

CI checks Build Link checker

tag badge license badge size badge

Podman Login is a GitHub Action to log in to a container image registry.

After logging in, you can work with the registry as an authenticated user, performing actions such as pushing an image, or pulling a private image. On GitHub runners, the authentication will be deleted at the end of each job as the workspace is cleaned up.

Also see push-to-registry and buildah-build for related actions that can make use of this authentication.

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

Action Inputs

Input Name Description Default
registry Hostname/domain of the container image registry such as quay.io, docker.io. Must be provided
username Username to login against the container image registry. Must be provided
password Password, encrypted password, or access token for username. Must be provided
logout By default, the action logs out of the container image registry at the end of the job (for self-hosted runners). Set this to false to disable this behaviour. true

Example

The example below shows how the podman-login action can be used to login to quay.io container image registry.

name: Login to Quay.io
on:
  push:

env:
  REGISTRY_USER: quayuser
  IMAGE_REGISTRY: quay.io
  REGISTRY_PASSWORD: ${{ secrets.REGISTRY_PASSWORD }}

jobs:
  login:
    name: Log in to image registry
    runs-on: ubuntu-20.04
    steps:

      - name: Login to Quay.io
        uses: redhat-actions/podman-login@v1
        with:
          username: ${{ env.REGISTRY_USER }}
          password: ${{ env.REGISTRY_PASSWORD }}
          registry: ${{ env.IMAGE_REGISTRY }}

      # Now you can push images, and pull private ones, from quay.io as 'quayuser'.