Docker Limitations in Artifactory

JFrog Artifactory Documentation

Products
JFrog Artifactory
Content Type
User Guide

The following are the limitations of Docker in Artifactory:

  • Key Length Limits: Key length limitations exist for Docker OCI and Helm OCI repositories to ensure proper operation and accessibility of repositories using the Docker subdomain method on cloud platforms:

    • 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.

    You will receive a warning when creating a repository or after creating a repository via API. You can create the repository, but no DNS record will be created, making the repository inaccessible unless you manage DNS records internally.

    If you are migrating from a self-hosted environment to the cloud platform, existing repositories with keys equal to or exceeding 63 characters may cause access issues.

  • Docker client limitations:

    • You cannot use a context path when providing the registry path, for example localhost:8082/artifactory is invalid

    • Docker will only send basic HTTP authentication when working against an HTTPS host or when using the insecure registry flag

    Artifactory offers solutions to these limitations with reverse proxies for self-hosted deployments, and out-of-the-box support for Docker repositories in cloud deployments of Artifactory as of version 5.8.