GitHub Container Registry
Use GHCR images as release artifacts.
At a glance
Section titled “At a glance”| Category | Registries & artifact repositories |
| Authentication | GitHub App or PAT with read:packages |
| Provider id | ghcr |
What it does
Section titled “What it does”- Repository and tag listing
- Digest resolution
Set up
Section titled “Set up”- Create a read (and optionally push) credential in the registry; prefer short-lived or workload-identity credentials.
- In Settings, Integrations, add the registry and store the credential as a Slipway secret reference.
- Use it as a service artifact source, or reference it from
slipway/docker-build@v1for pushes.
Configuration
Section titled “Configuration”Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.
provider: ghcrconfig: owner: acmecredentials: secret://GHCR_TOKENRelated
Section titled “Related”- Integrations overview
- Secrets for how credentials are stored and masked
- Webhooks and events for the events integrations subscribe to