---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia IT Operations Management
ft:clusterId :
- itom
bundleId :
- itom
workflow :
- Technology
---
# Disable Docker container CI discovery
# Disable Docker container CI discovery {#ariaid-title1}
Release version: Australia
Updated December 19, 2024
 1 minute to read
Configure Docker discovery to collect image CIs only, instead of both image and container CIs.
## Before you begin
* Verify that you have at least version 1.31.0 of Discovery and Service Mapping Patterns.
* Check your entitlements to determine whether you have access to 2026 Packaging SKU.
Role required: discovery_admin (granted automatically with 2026 Packaging SKU)
## About this task
In large environments, container instances can generate a high volume of CIs. The sn_itom_pattern.bring_discovery_container system property controls
whether the Kubernetes, Kubernetes Event, Docker Pattern, and Amazon AWS - ECS patterns discover both Docker container and Docker image CIs, or only Docker image CIs.{#disable-docker-container-discovery__disable-container-discovery-licensing-v4-context-1}
By default, the property is set to true and both Docker Container \[cmdb_ci_docker_container\] and Docker Image \[cmdb_ci_docker_image\] are populated. When set to false, only Docker Image
\[cmdb_ci_docker_image\] is populated.
## Procedure
1. In the navigation filter, enter sys_properties.list.
2. In the Name column, search for sn_itom_pattern.bring_discovery_container.
3. Select the sn_itom_pattern.bring_discovery_container system property.
4. In the Value field, enter false.
To discover both Docker container and Docker image CIs, set the value to true.
5. Select Update.
{#disable-docker-container-discovery__steps_iyx_vsf_gjc}
## What to do next
Run discovery again to apply the changes.