Promote an image using policiesEstimated reading time: 3 minutes
This topic applies to Docker Enterprise.
The Docker Enterprise platform business, including products, customers, and employees, has been acquired by Mirantis, inc., effective 13-November-2019. For more information on the acquisition and how it may affect you and your business, refer to the Docker Enterprise Customer FAQ.
Docker Trusted Registry allows you to create image promotion pipelines based on policies.
In this example we will create an image promotion pipeline such that:
- Developers iterate and push their builds to the
- When the team creates a stable build, they make sure their image is tagged
- When a stable build is pushed to the
dev/websiterepository, it will automatically be promoted to
qa/websiteso that the QA team can start testing.
With this promotion policy, the development team doesn’t need access to the QA repositories, and the QA team doesn’t need access to the development repositories.
Configure your repository
Once you’ve created the repository, navigate to the repository page on the DTR web interface, and select the Promotions tab.
Only administrators can globally create and edit promotion policies. By default users can only create and edit promotion policies on repositories within their user namespace. For more information on user permissions, see Authentication and Authorization.
Click New promotion policy, and define the image promotion criteria.
DTR allows you to set your promotion policy based on the following image attributes:
|Tag name||Whether the tag name equals, starts with, ends with, contains, is one of, or is not one of your specified string values||Promote to Target if Tag name ends in
|Component name||Whether the image has a given component and the component name equals, starts with, ends with, contains, is one of, or is not one of your specified string values||Promote to Target if Component name starts with
|Vulnerabilities||Whether the image has vulnerabilities – critical, major, minor, or all – and your selected vulnerability filter is greater than or equals, greater than, equals, not equals, less than or equals, or less than your specified number||Promote to Target if Critical vulnerabilities =
|License||Whether the image uses an intellectual property license and is one of or not one of your specified words||Promote to Target if License name =
Now you need to choose what happens to an image that meets all the criteria.
Select the target organization or namespace and repository where the image is going to be pushed. You can choose to keep the image tag, or transform the tag into something more meaningful in the destination repository, by using a tag template.
In this example, if an image in the
dev/website is tagged with a word that
ends in “stable”, DTR will automatically push that image to the
repository. In the destination repository the image will be tagged with the
timestamp of when the image was promoted.
Everything is set up! Once the development team pushes an image that complies
with the policy, it automatically gets promoted. To confirm, select the Promotions tab on the
You can also review the newly pushed tag in the target repository by navigating to
qa/website and selecting the Tags tab.