Enabling GitHub Container Registry for your organization

In an organization, organization admins can allow organization members to publish public or private container images to GitHub Container Registry.

GitHub Packages is available with GitHub Free, GitHub Pro, GitHub Free for organizations, GitHub Team, GitHub Enterprise Cloud, GitHub Enterprise Server 2.22, and GitHub One.


GitHub Packages is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access GitHub Container Registry since these accounts are billed by repository. For more information, see "GitHub's products."

Did this doc help you?

Note: GitHub Container Registry is currently in public beta and subject to change. Currently, GitHub Container Registry only supports Docker image formats. During the beta, storage and bandwidth is free. For more information, see "About GitHub Container Registry."

Before organization members can publish container images to GitHub Container Registry, an organization admin must enable package creation.

  1. In the top right corner of GitHub, click your profile photo, then click Your profile.

    Profile photo

  2. On the left side of your profile page, under "Organizations", click the icon for your organization.

    organization icons

  3. Under your organization name, click Settings.

    Organization settings button

  4. In the left sidebar, click Member privileges.

    Member privileges option in org settings

  5. Under "Package creation", choose whether you want to enable the creation of public or private container images.

    • To enable organization members to create a public container image, click Public.
    • To enable organization members to create a private container image that is only visible to other organization members, click Private. You can further customize the visibility of a private container image. For more information, see "Configuring access control and visibility for container images."

    Options to enable public or private packages

Did this doc help you?