actions/push-to-registry
1
0
Fork 0
mirror of https://github.com/redhat-actions/push-to-registry.git synced 2025-02-22 18:21:20 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add note about ubuntu/Podman version

Browse source 
Fixes #26

Signed-off-by: Tim Etchells <tetchell@redhat.com>
This commit is contained in:
Tim Etchells 2021-02-22 14:10:22 -05:00
parent 63909e5fa4
commit 2b929ada2e
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
README.md
View file

@ -101,12 +101,12 @@ The example below shows how the `push-to-registry` action can be used to push an
```yaml
name: Build and Push Image
on: [push]
on: [ push ]
jobs:
build:
name: Build and push image
runs-on: ubuntu-latest
runs-on: ubuntu-20.04
env:
IMAGE_NAME: my-app
IMAGE_TAGS: latest v1
@ -148,6 +148,11 @@ If the image to push is present in both the Docker and Podman image storage, the
If the action pulled an image from the Docker image storage into the Podman storage, it will be cleaned up from the Podman storage before the action exits.
## Note about GitHub runners and Podman
We recommend using `runs-on: ubuntu-20.04` since it has a newer version of Podman.
If you are on `ubuntu-18.04` (which is currently aliased to [`ubuntu-latest`](https://github.com/actions/virtual-environments/issues/1816)) your workflow will use an older version of Podman and may encounter issues such as [#26](https://github.com/redhat-actions/push-to-registry/issues/26).
## Troubleshooting
Note that quay.io repositories are private by default.<br>