注意:这种包类型可能不适用于� 的实例,� 为站点管理员可以启用或禁用每种支持的包类型。 有关详细信息,请参阅“为企业配置包支持”。
About Docker support
When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images.
Authenticating to GitHub Packages
You need an access token to publish, install, and delete private, internal, and public packages.
You can use a personal access token to authenticate to GitHub Packages or the GitHub Enterprise Server API. When you create a personal access token, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a personal access token, see "About permissions for GitHub Packages."
To authenticate to a GitHub Packages registry within a GitHub Actions workflow, you can use:
GITHUB_TOKEN
to publish packages associated with the workflow repository.- a personal access token with at least
packages:read
scope to install packages associated with other private repositories (whichGITHUB_TOKEN
can't access).
有关 GitHub Actions 工作流中使用的 GITHUB_TOKEN
的详细信息,请参阅“工作流中的身份验证”。
Authenticating with a personal access token
You must use a personal access token with the appropriate scopes to publish and install packages in GitHub Packages. For more information, see "About GitHub Packages."
You can authenticate to GitHub Packages with Docker using the docker
login command.
To keep your credentials secure, we recommend you save your personal access token in a local file on your computer and use Docker's --password-stdin
flag, which reads your token from a local file.
If your instance has subdomain isolation enabled:
$ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin
If your instance has subdomain isolation disabled:
$ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin
To use this example login command, replace USERNAME
with your GitHub Enterprise Server username, HOSTNAME
with the URL for your GitHub Enterprise Server instance, and ~/TOKEN.txt
with the file path to your personal access token for GitHub Enterprise Server.
For more information, see "Docker login."
Publishing an image
注意: GitHub Packages Docker 注册表 将在未来的 GitHub Enterprise Server 版本中被 Container registry 取代,后者提供了改进的容器支持。
Note: Image names must only use lowercase letters.
GitHub Packages supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "Docker tag" in the Docker documentation.
在发布包后,您可以在 GitHub 上查看该包。 有关详细信息,请参阅“查看包”。
-
Determine the image name and ID for your docker image using
docker images
.$ docker images > <� > > REPOSITORY TAG IMAGE ID CREATED SIZE > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB
-
Using the Docker image ID, tag the docker image, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, HOSTNAME with the hostname of your GitHub Enterprise Server instance, and VERSION with package version at build time.
If your instance has subdomain isolation enabled:
$ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
If your instance has subdomain isolation disabled:
$ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
-
If you haven't already built a docker image for the package, build the image, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, VERSION with package version at build time, HOSTNAME with the hostname of your GitHub Enterprise Server instance, and PATH to the image if it isn't in the current working directory.
If your instance has subdomain isolation enabled:
$ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
If your instance has subdomain isolation disabled:
$ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
-
Publish the image to GitHub Packages.
If your instance has subdomain isolation enabled:
$ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
If your instance has subdomain isolation disabled:
$ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
Note: You must push your image using
IMAGE_NAME:VERSION
and not usingIMAGE_NAME:SHA
.
Example publishing a Docker image
These examples assume your instance has subdomain isolation enabled.
You can publish version 1.0 of the monalisa
image to the octocat/octo-app
repository using an image ID.
$ docker images
> REPOSITORY TAG IMAGE ID CREATED SIZE
> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB
# Tag the image with OWNER/REPO/IMAGE_NAME
$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0
# Push the image to GitHub Packages
$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0
You can publish a new Docker image for the first time and name it monalisa
.
# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
# Assumes Dockerfile resides in the current working directory (.)
$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 .
# Push the image to GitHub Packages
$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0
Downloading an image
注意: GitHub Packages Docker 注册表 将在未来的 GitHub Enterprise Server 版本中被 Container registry 取代,后者提供了改进的容器支持。
You can use the docker pull
command to install a docker image from GitHub Packages, replacing OWNER with the name of the user or organization account that owns the repository, REPOSITORY with the name of the repository containing your project, IMAGE_NAME with name of the package or image, HOSTNAME with the host name of your GitHub Enterprise Server instance, and TAG_NAME with tag for the image you want to install.
If your instance has subdomain isolation enabled:
$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
If your instance has subdomain isolation disabled:
$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
Note: You must pull the image using IMAGE_NAME:VERSION
and not using IMAGE_NAME:SHA
.