Using the latest version?
JFrog Container Registry Guide
Deploying a Single Artifact
To deploy a single artifact, simply fill in the fields in the Deploy dialog and click "Deploy".
Deploying According to Layout
The Deploy dialog displays the repository package type and layout configured. To deploy your package according to the configured layout, check Deploy According to Layout.
JFrog Container Registry displays entry fields corresponding to the layout tokens for you to fill in.
Deploying Multiple Files
To deploy multiple files together, set the deploy Type to Multi, fill in the rest of the fields in the dialog and click "Deploy".
Deploying an Artifact Bundle
An artifact bundle is deployed as a set of artifacts packaged in an archive with one of the following supported extensions: zip, tar, tar.gz, tgz.
When you specify that an artifact should be deployed as a bundle, JFrog Container Registry will extract the archive contents when you deploy it.
File structure within the archive
Artifacts should be packaged within the archive in the same file structure with which they should be deployed to the target repository.
To deploy an artifact bundle, in the Deploy dialog, first upload the archive file you want to deploy.
Check the Deploy as Bundle Artifact checkbox and click Deploy.
Deploying to a Virtual Repository
JFrog Container Registry supports deploying artifacts to a virtual repository.
To enable this, you first need to designate one of the local repositories that is aggregated by the virtual repository as a deployment target. This can be done through the UI by setting the Default Deployment Repository in the Basic Settings of the Edit Repository screen.
Once the deployment target is configured, you may deploy artifacts to it using any packaging format client configured to work with JFrog Container Registry. For example,
docker push and
You can also use JFrog Container Registry's REST API to deploy an artifact and use the virtual repository key in the path to deploy.
If you do specify a Default Deployment Repository for a virtual repository, the corresponding Set Me Up dialog for the repository will also include instructions and code snippets for deploying to that repository.
The most common reasons for a rejected deployment are:
- Lack of permissions
- A conflict with the target repository's includes/excludes patterns
- A conflict with the target repository's snapshots/releases handling policy.