GitOps GitHub Container Registry (GHCR) integration
The GitHub Container registry allows you to host and manage your Docker container images in your personal or organisation account on GitHub. One of the benefits is that permissions can be defined for the Docker image independent from any repository. Thus, your repository could be private and your Docker image public.
For information on adding a GitHub Container registry integration in Codefresh, see Container registry GitOps integrations.
Prerequisites
Before you configure settings in Codefresh to integrate GitHub container registry:
- Make sure you have a personal access token with the correct scopes or create one.
You need at least the following scopes:write:packagesread:packagesdelete:packagesrepo(if your repository is private; do not select if it is public)
For detailed information, see the Authenticating to the Container registry.
GitHub Container registry (GHCR)-GitOps integration settings in Codefresh
| Setting | Description |
|---|---|
| Integration name | A friendly name for the integration. This is the name you will reference in the third-party CI platform/tool. |
| All Runtimes/Selected Runtimes | The runtimes in the account with which to share the integration resource. The integration resource is created in the Git repository with the shared configuration, within resources. The exact location depends on whether the integration is shared with all or specific runtimes:
|
| Domain | The GitHub registry domain and is set to ghcr.io. |
| Username | Your GitHub username. |
| GitHub Token | Your GitHub PAT (personal access token). |
| Test Connection | Click to verify that you can connect to the specified instance before you commit changes. |
For how-to instructions, see Configure container registry integrations for GitOps in Codefresh and Edit/delete container registry integrations for GitOps in Codefresh.
Related articles
Shared Configuration Repository
Image enrichment with GitOps integrations
CI GitOps integrations
Issue-tracking GitOps integrations