Docker Repository Key Length Limitation on Cloud Platforms

JFrog Artifactory Documentation

Products
JFrog Artifactory
Content Type
User Guide
ft:sourceType
Paligo

To ensure proper operation and accessibility of repositories using the Docker subdomain method on cloud platforms, it is important to adhere to the following repository key length limitations.

These key length limitations apply to Docker OCI and Helm OCI repositories.

Key Length Limits

  • Hard Limit: The maximum allowable length for repository keys is 63 characters. This limit is enforced strictly and cannot be exceeded.

  • Soft Limit: The soft limit is calculated as 63 - (length of server name + 1). This means the effective length for the repository key may be shorter, depending on the combined length of the server name.

    For example, if the server name is 'myserver', which is 8 characters, then the Soft Limit is 63 - (8+1), which is 54.

  • Warning: Customers will receive a warning during the repository creation process. The warning is provided in the user interface when creating a repository or after creating a repository via API. While the repository can be created, no DNS record will be created, making the repository inaccessible unless you manage DNS records internally.

Migrating from Self-Hosted to Cloud Platform

Customers migrating from a self-hosted environment to the cloud platform should be aware that existing repositories with keys equal to or exceeding 63 characters may experience access issues post-migration.