Publishing
Setup
- Browse to
.github/workflows/ci.yaml
file. - Take note of the required github secrets. E.g.
DOCKERHUB_TOKEN
. - Add the repo secrets.
Quay.io
For the Quay.io registry, you'll need to manually create an image repository. It does not create one upon first push like Docker Hub.
- Create a quay.io image repository.
- Give
write
access to a robot for the newly created image repository.
Publishing
Publishing images is done through the ci github action. The action is automatically triggered grabs the build variables from the VERSION
, CHECKSUM
, and LS
variables. The github action also creates a release.
The name of the image is taken from the repository name after docker-
. So, repo docker-etherpad
would have an image name of etherpad
.
Both the current version tag and the latest tag are released.
Github Repository
- Browse to the Actions tab.
- Click on the
ci
workflow. - Manually trigger the workflow using the app version and image (ls) version.
Github Packages
By default, a ghcr.io
package is published as private and so after the initial release to the ghcr.io
registry, the package will need to be converted to a public package if you want anyone to use it.
- See Configuring visibility of container images for your personal account.
- You may also set connect your repository to your container image/package. See Connecting a repository to a container image.
Troubleshooting
See Troubleshooting