mirror of
https://github.com/redhat-actions/podman-login.git
synced 2025-02-23 10:31:21 +01:00
58 lines
3.1 KiB
Markdown
58 lines
3.1 KiB
Markdown
# podman-login
|
|
[](https://github.com/redhat-actions/podman-login/actions?query=workflow%3A%22CI+checks%22)
|
|
[](https://github.com/redhat-actions/podman-login/actions?query=workflow%3ABuild)
|
|
[](https://github.com/redhat-actions/podman-login/actions?query=workflow%3A%22Link+checker%22)
|
|
<br>
|
|
<br>
|
|
[](https://github.com/redhat-actions/podman-login/tags)
|
|
[](./LICENSE)
|
|
[](./dist)
|
|
|
|
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](https://github.com/redhat-actions/push-to-registry)** and **[buildah-build](https://github.com/redhat-actions/buildah-build)** for related actions that can make use of this authentication.
|
|
|
|
This action only runs on `Linux`, as it uses [podman](https://github.com/containers/Podman) to perform the log in. [GitHub's Ubuntu action runners](https://github.com/actions/virtual-environments#available-environments) come with Podman preinstalled. If you are not using those runners, you must first [install Podman](https://podman.io/getting-started/installation).
|
|
|
|
<a id="action-inputs"></a>
|
|
|
|
## 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 log in 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 log in to `quay.io` container image registry.
|
|
|
|
```yaml
|
|
name: Log in 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: Log in 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'.
|
|
```
|