--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management Release : - australia ft:locale : - de-DE ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Container image discovery # Container image discovery {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer The Discovery and Service Mapping Patterns application uses the Scan Container Image pattern to discover Docker images and OS packages data. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. ## Request apps on the Store {#container_image_scan_pattern__section_sv2_vw5_5mb} Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://docs.servicenow.com/bundle/store-release-notes/page/release-notes/store/sn-store-release-notes.html).{#container_image_scan_pattern__inline-send-to-store} ## Verify the REST API Permissions {#container_image_scan_pattern__id_v1m_f3m_jcc} Download the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.{#container_image_scan_pattern__cloud-discovery-api-paragraph} For information about performing a container image scan, see [Scan container images](https://servicenow-prod.fluidtopics.net/UTbSIVntApDwhDpF77lahA "Enable container image scanning using the Aqua Trivy tool."). The Scan Container Image pattern supports Aqua Trivy starting with version 0.44.0. The last version validated is 0.68.2. Starting with Discovery and Service Mapping Patterns version 1.18.0, the Scan Container Image pattern supports scanning container images in the following repositories: * Public repositories * Self-hosted private repositories * Amazon Elastic Container Registry (Amazon ECR), both public and private repositories {#container_image_scan_pattern__ul_zqh_ccq_dcc} Starting with version 1.27.0, Discovery and Service Mapping Patterns enables you to control whether to link software packages to containers or only to images. For more information, see [Link software package information to images only](https://servicenow-prod.fluidtopics.net/o1jSHzInu0gTLe0cHSba7A "Link software package information to images rather than containers to avoid empty records that associate to short-lived containers."). ## Data collected by Discovery for container image scans {#container_image_scan_pattern__section_bfy_ggh_fwb} Discovery populates the data in the CMDB when running the Scan Container Image pattern.{#container_image_scan_pattern__table_x24_ywh_fwb__entry__2} | Field | Description | |-|-| | Application \[cmdb_ci_appl\] table || | Name \[name\] | Name of the container application. The MSSQL application record required name format: ApplicationTableName@containerName Example: MSFT SQL Instance@/sql1 | | Container environment variables \[cmdb_container_environment_variables\] table || | Container \[container\] | Name of the container. | | Key \[key\] | Name of the Container environment variable. | | Value \[value\] | Container environment variable value. | [ ] {#container_image_scan_pattern__table_x24_ywh_fwb} ## Temporary tables for container image scans {#container_image_scan_pattern__section_ag1_f3m_jwb} Hinweis: If you're using the 1.0.98 version to collect the data, the enriched scripts are supported only with MSSQL. {#container_image_scan_pattern__table_kkw_yng_mwb__entry__2} | Field | Description | |-|-| | Container image scan Status \[sn_itom_pattern_container_image_scan_status\] || | Image \[image\] | Name of the container image. | | Message \[message\] | Errors or issues with the scanning process. | | CI Class \[ci_class\] | The image CI class based on the image command details. | | Discovery status \[discovery_status\] | The discovery status record of the image scan. | | Scan Status \[scan_status\] | The scan status. The available values are: * None - The image isn't scanned yet. * In Progress - The image scan is in progress. Hinweis: If one or more images are in progress, the next scan won't trigger. * Scanned - The image was scanned successfully. * Error - A problem occurred during the image scan. Check the message column for details. * Skipped - The image URL isn't formed properly or isn't reachable. {#container_image_scan_pattern__ul_lkw_yng_mwb} | | Container image OS packages \[sn_itom_pattern_container_image_os_packages\] table || | Image \[image\] | Name of the container image. | | Package Name \[package_name\] | Name of the software package. | | Package Version \[package_version\] | Version of the software package. | | Package Maintainer \[package_maintainer\] | Name of the package maintainer. | | Container Enrich Scripts \[sn_itom_pattern_container_enrich_scripts\] || | Active \[active\] | Whether the enrich script state is active. | | CI Type \[ci_type\] | The CI type to which the enrich script is applicable. | | Order \[order\] | Execution order of a particular script. | | Script \[script\] | The enrich script name. | [Tabelle : 1. Data collected during horizontal discovery] {#container_image_scan_pattern__table_kkw_yng_mwb} ## Relationships {#container_image_scan_pattern__section_i3d_jgh_fwb} These relationships are created to support the container image discovery. {#container_image_scan_pattern__table_d3z_vg3_fwb__entry__3} | CI | relation | CI | |-|-|-| | cmdb_ci_appl | Runs on::Runs | cmdb_ci_oslv_container | | cmdb_ci_docker_container | Extends from | cmdb_ci_oslv_container | | cmdb_ci_oslv_container | Extends from | cmdb_ci | | cmdb_ci_oslv_container | Reference only | cmdb_container_environment_variables | | container_enrich_scripts | Extends from | sys_metadata | | cmdb_container_environment | Extends from | cmdb_key_value | | cmdb_ci_db_mssql_instance | Runs::Runs on | cmdb_ci_docker_container | [ ] {#container_image_scan_pattern__table_d3z_vg3_fwb} **Zugehörige Konzepte** * [Docker virtualization](https://servicenow-prod.fluidtopics.net/pJHgjb8Eq9BFqZRXvpu3WQ "Discovery uses the Docker Pattern to collect data about specific objects in a Docker engine, running on a Linux host.") * [Kubernetes discovery using patterns](https://servicenow-prod.fluidtopics.net/DxwB0lAeof0qBgmSxIZ~yg "The ServiceNow ITOM Visibility finds Kubernetes and OpenShift components using patterns and creates application services containing them. Discovery also finds Kubernetes events and frequently updates the CMDB to reflect the dynamic Kubernetes environment.")