Reviewed-on: https://codeberg.org/forgejo/website/pulls/323 # Conflicts: # v1.19/admin/command-line.md # v1.19/admin/config-cheat-sheet.md # v1.19/admin/database-preparation.md # v1.19/admin/email-setup.md # v1.19/admin/incoming-email.md # v1.19/admin/index.md # v1.19/admin/logging-documentation.md # v1.19/admin/reverse-proxy.md # v1.19/admin/seek-assistance.md # v1.19/admin/upgrade.md # v1.19/developer/code-forgejo-org.md # v1.19/developer/index.md # v1.19/index.md # v1.19/license.md # v1.19/user/agit-support.md # v1.19/user/api-usage.md # v1.19/user/authentication.md # v1.19/user/email-settings.md # v1.19/user/first-repository.md # v1.19/user/index.md # v1.19/user/issue-pull-request-templates.md # v1.19/user/issue-tracking-basics.md # v1.19/user/labels.md # v1.19/user/linked-references.md # v1.19/user/merge-message-templates.md # v1.19/user/oauth2-provider.md # v1.19/user/packages/cargo.md # v1.19/user/packages/chef.md # v1.19/user/packages/composer.md # v1.19/user/packages/conan.md # v1.19/user/packages/conda.md # v1.19/user/packages/container.md # v1.19/user/packages/generic.md # v1.19/user/packages/helm.md # v1.19/user/packages/index.md # v1.19/user/packages/maven.md # v1.19/user/packages/npm.md # v1.19/user/packages/nuget.md # v1.19/user/packages/pub.md # v1.19/user/packages/pypi.md # v1.19/user/packages/rubygems.md # v1.19/user/packages/storage.md # v1.19/user/packages/vagrant.md # v1.19/user/project.md # v1.19/user/protection.md # v1.19/user/push-options.md # v1.19/user/push-to-create.md # v1.19/user/repo-permissions.md # v1.19/user/webhooks.md # v1.19/user/wiki.md # v1.20/user/semver.md
2.3 KiB
title | license | origin_url |
---|---|---|
Container Registry | Apache-2.0 | faa28b5a44/docs/content/doc/usage/packages/container.en-us.md |
Publish Open Container Initiative compliant images for your user or organization. The container registry follows the OCI specs and supports all compatible images like Docker and Helm Charts.
Requirements
To work with the Container registry, you can use the tools for your specific image type.
The following examples use the docker
client.
Login to the container registry
To push an image or if the image is in a private registry, you have to authenticate:
docker login forgejo.example.com
If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/developers/api-usage.en-us.md#authentication" >}}) instead of the password.
Image naming convention
Images must follow this naming convention:
{registry}/{owner}/{image}
For example, these are all valid image names for the owner testuser
:
forgejo.example.com/testuser/myimage
forgejo.example.com/testuser/my-image
forgejo.example.com/testuser/my/image
NOTE: The registry only supports case-insensitive tag names. So image:tag
and image:Tag
get treated as the same image and tag.
Push an image
Push an image by executing the following command:
docker push forgejo.example.com/{owner}/{image}:{tag}
Parameter | Description |
---|---|
owner |
The owner of the image. |
image |
The name of the image. |
tag |
The tag of the image. |
For example:
docker push forgejo.example.com/testuser/myimage:latest
For more information please check the docker push documentation page.
Pull an image
Pull an image by executing the following command:
docker pull forgejo.example.com/{owner}/{image}:{tag}
Parameter | Description |
---|---|
owner |
The owner of the image. |
image |
The name of the image. |
tag |
The tag of the image. |
For example:
docker pull forgejo.example.com/testuser/myimage:latest