Using the latest version?
JFrog Container Registry Guide
Working with JFrog Container Registry Cloud
Due to limitations of the Docker client, in JFrog Container Registry Cloud there is a special configuration for each server with a sub-domain.
You need to create a new Docker enabled local repository named
Then, use the following address when working with the Docker client:
3. Setting Up Authentication
When using JFrog Container Registry with Docker V1, you need to set your credentials manually by adding the following section to your
4. Pushing and Pulling Images
Pushing and pulling images when using Docker V1 is done in the same way as when using Docker V2. Please refer to Pushing and Pulling Images under the Docker Repositories page.
Browsing Docker Repositories
JFrog Container Registry stores docker images in a layout that is made up of 2 main directories:
- .images: Stores all the flat docker images.
- repositories: Stores all the repository information with tags (similar to how repositories are stored in the Docker Hub).
In addition, JFrog Container Registry annotates each deployed docker image with two properties:
- docker.imageId: The image id
- docker.size: The size of the image in bits
Deployed tags are also annotated with two properties:
- docker.tag.name: The tag name
- docker.tag.content: The id of the image that this tag points to
Viewing the Docker Images Tree
JFrog Container Registry lets you view the complete images tree for a specific image directly from the UI in a similar way to what you would get from the
docker images --tree command.
In the Artifacts module Tree Browser, drill down to select the image you want to inspect. The metadata is displayed in the Docker Ancestry tab.
Viewing Individual Docker image Information
In the Artifacts module Tree Browser, drill down to select image you want to inspect. The metadata is displayed in the Docker Info tab.
Searching for Docker Images
In addition to other properties related to Docker repositories, you can also search for repositories using a property called
docker.repoName, which represents the repository name (e.g., "library/ubuntu").
Promoting Docker Images with V1
Promoting Docker images with Docker V1 is done in exactly the same way as when Promoting Images with Docker V2.
Migrating a V1 repository to V2
We recommend using Docker V2 repositories when possible (provided your Docker client is version 1.6 and above).
If you have an existing Docker V1 repository, you can migrate its content into a V2 repository using the following endpoint with cURL:
|Source repository key (For example, docker-local as used in this page)|
|The target Docker V2 repository to migrate to (For example, docker-local2 as used in this page). The repository should be created before running the |
|An optional docker repository name to migrate, if null - the entire source repository will be migrated. Default: ""|
|An optional tag name to promote, if null - the entire docker repository will be promoted. Default: ""|
An example for migrating the docker image
"jfrog/ubuntu" with all of it's tags from
docker-local2 using cURL would be:
Deletion and Cleanup
JFrog Container Registry natively supports removing tags and repositories and complies with the Docker Hub Spec.
Deletion of Docker tags and repositories automatically cleans up any orphan layers that are left (layers not used by any other tag/repository).
Currently, the Docker client does not support DELETE commands, but deletion can be triggered manually using cURL. Here are some examples:
Any empty directories that are left following removal of a repository or tag will automatically be removed during the next folder pruning job (which occurs every 5 minutes by default).
Using a Self-signed SSL Certificate
From Docker version 1.3.1, you can use self-signed SSL certificates with
docker push/pull commands, however for this to work, you need to specify the
--insecure-registry daemon flag for each insecure registry.
For full details please refer to the Docker documentation.
For example, if you are running Docker as a service, edit the
/etc/default/docker file, and append the
--insecure-registry flag with your registry URL to the DOCKER_OPTS variable as in the following example:
For this to take effect, you need to restart the Docker service.
If you are using Boot2Docker, please refer to the Boot2Docker documentation for Insecure Registry.
If you do not make the required modifications to the
--insecure-registry daemon flag, you should get the following error:
Using previous versions of Docker
Alternative Proxy Servers
In addition to NGINX, you can setup JFrog Container Registry to work with Docker using Apache.
The sample configuration below configures SSL on port 443 and a server name of
If you want to use multiple repositories, you need to copy the NGINX configuration and bind different ports to each local repository in JFrog Container Registry.
When binding a port other than 443, note that the configuration for the proxy header must be appended with the port number on the
For example, for a server running on port 444 you should write
proxy_set_header Host $host:444.
Docker Repository Path and Domain
When accessing a Docker repository through JFrog Container Registry, the repository URL must be prefixed with api/docker in the path.
You can copy the full URL from the UI using Set Me Up when the repository is selected in the Tree Browser.
For example, if you are using JFrog Container Registry standalone or as a local service, you would access your Docker repositories using the following URL:
Also, the domain of your Docker repository must be expressed as an explicit IP address. The only exception is when working locally, you can use the localhost domain name as the proxy pass.