This rule enables you to control the docker image and version which will be (not) used across your different repositories.
Mixing and matching your base operating systems for each Docker image can add cognitive load and maintain overhead (e.g. you need to keep track of package managers for different distributions of Linux).
Managing multi Docker images on multi repositories is a tricky task but once accomplished - can reduce the number of production mishaps because it is easier to maintain narrowed distribution of different docker images.
- White-listing - create aligment of images and/or their versions across different projects
- Black-listing - deny the usage of depraceted images (e.g jenkins/jenkins) and/or versions across the entire dev stack
When does this rule fail?
When the Docker image used in the repository doesn't follow the custom rule pattern.
How to fix?
- Change the image type in the dockerfiles according to your org policy
- Push the code changes to your branch:
$ git commit -m "Update Docker image according to Datree policy" $ git push
- Datree's policy check automatically ensures the Docker image used in the repository meets the org requirements
|Activate Docker image custom policy|