Note: GitHub Packages is currently in beta for GitHub Enterprise Server 2.22. To join the beta for your your GitHub Enterprise Server instance, use the sign-up form.
Note: After you've been invited to join the beta, follow the instructions from your account representative to enable GitHub Packages for your GitHub Enterprise Server instance.
Note: GitHub Packages on GitHub Enterprise Server does not currently support clustering.
GitHub Packages on GitHub Enterprise Server uses external blob storage to store your packages.
After enabling GitHub Packages for your GitHub Enterprise Server instance, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of GitHub Packages, and the setup guidelines can vary by storage provider.
Supported external storage providers
- Amazon Web Services (AWS) S3
To enable GitHub Packages and configure third-party storage, see:
Choose which package ecosystems you'd like to enable, disable, or set to read-only on your your GitHub Enterprise Server instance. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "Configuring package ecosystem support for your enterprise."
If subdomain isolation is enabled for your GitHub Enterprise Server instance, which is required to use GitHub Packages with Docker, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as
npm.HOSTNAME. Make sure each package host URL includes
You can create the certificate manually, or you can use Let's Encrypt. If you already use Let's Encrypt, you must request a new TLS certificate after enabling GitHub Packages. For more information about package host URLs, see "Enabling subdomain isolation." For more information about uploading TLS certificates to GitHub Enterprise Server, see "Configuring TLS."