actions/push-to-registry
1
0
Fork 0
mirror of https://github.com/redhat-actions/push-to-registry.git synced 2025-05-19 21:54:46 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Support/node20 (#93)

Browse source 
* Update action.yml to use node20

* Update README.md with newer runner versions and fix typo

* Update all workflows to use newer action versions and runner environments
This commit is contained in:
EusebioTrigo 2024-03-05 14:48:07 +01:00 • committed by GitHub
parent e85426e5e2
commit 0fa2dca2e8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
11 changed files with 31 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -101,10 +101,10 @@ on: [ push ]
jobs:
build:
name: Build and push image
runs-on: ubuntu-20.04
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v2
- uses: actions/checkout@v4
- name: Build Image
id: build-image
@ -144,13 +144,13 @@ 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.
We recommend using `runs-on: ubuntu-22.04` since it has a newer version of Podman.
If you are on `ubuntu-18.04` or any other older versions of ubuntu 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).
If you are on `ubuntu-20.04` or any other older versions of ubuntu 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>
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.
Simiarly, if you receive a 403 Forbidden from GHCR, you may have to update the Package Settings. Refer to [this issue](https://github.com/redhat-actions/push-to-registry/issues/52).
Similarly, if you receive a 403 Forbidden from GHCR, you may have to update the Package Settings. Refer to [this issue](https://github.com/redhat-actions/push-to-registry/issues/52).