---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Map MID Server to container image repository

# Map MID Server to container image repository {#ariaid-title1}

* Release version: Yokohama
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

If network access or datacenter location requires a specific MID Server, map MID Server to a private container image repository.

## Before you begin

* Verify that you have at least version 1.30.2 of Discovery and Service Mapping Patterns.
* Verify that the Linux MID Server has the following requirements:
  * 8GB RAM with 4GB for the Java Virtual Machine (JVM).
  * MID Server Capability configured to Scan Container Images. For more information on configuring capabilities, see [MID Server capabilities](https://www.servicenow.com/docs/access?context=mid-server-capabilities&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US).
  * Can access the image repository.
  * Has Aqua Trivy, starting 0.44.0, installed on the MID Server. The last version validated is 0.68.2. For more information on installing Aqua Trivy, see the [Container Image scan feature overview \[KB1218504\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1218504) article in the Now Support Knowledge Base.
  {#map-mid-server-container-repository__ul_j4r_5kv_42c}
* Verify that the container image repository credentials are configured for the private repositories. For more information, see [Create and test your credentials](https://www.servicenow.com/docs/access?context=t_CreateCredential&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) and [Container image repository credentials](https://www.servicenow.com/docs/access?context=container-image-repo-credential&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).
* Verify that a container image discovery has run for Docker, Kubernetes, or Amazon Elastic Container Service (Amazon ECS) discovery. For more information, see:
  * [Docker virtualization](https://servicenow-prod.fluidtopics.net/moBGxMCYkup3w1gzKDxSWg "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/Nq0fHYmeSm4QYmSRUrjWJA "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.")
  * [Amazon ECS resource discovery with Patterns](https://servicenow-prod.fluidtopics.net/tRIJbSQlM~dhgQQzyIz54g "The ServiceNow Discovery application uses the Amazon AWS - ECS pattern to find resources managed by the Amazon Elastic Container Service (Amazon ECS). This includes resources that are run on the Fargate launch type. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")
  {#map-mid-server-container-repository__ul_gky_rky_f3c}
* Verify that the Container Repository table contains the repository names required for this mapping. You can view the container repository list by entering <kbd class="ph userinput">cmdb_ci_container_repository_list.do</kbd> in the navigation filter.
{#map-mid-server-container-repository__ul_prerequisites}

Role required: discovery_admin

## About this task

By default, container image scanning selects a MID Servers with the Scan Container Images capability from the available MID Servers. You can configure the Image Registry to Mid Server Mapping table to map specific MID Servers to private repositories.

## Procedure

1. Navigate to AllSystem DefinitionTables.
2. In the Label column, enter <kbd class="ph userinput">Image Registry to Mid Server Mapping</kbd>.
3. Select the Image Registry to Mid Server Mapping table.
4. In the Related Links section, select Show List.
5. Select New.
6. In the form, fill in the fields:  
   {#map-mid-server-container-repository__table_field_configuration__entry__2}

   | Field | Description |
   |-|-|
   | Registry URL | Registry domain or host from the Container Repository table, up to the first slash. For example, if the full path is registry.example.com/project/image, enter <kbd class="ph userinput">registry.example.com</kbd>. |
   | Mid server | Linux MID Server for this repository that has the Scan Container Images capability configured. |
   | Active | Option for enabling this mapping. |
   [Table 1. Image Registry to Mid Server Mapping fields]

   {#map-mid-server-container-repository__table_field_configuration}
7. Select Submit.

## What to do next

Scan the container images. For more information, see [Scan container images](https://servicenow-prod.fluidtopics.net/7~3F3xLe_VZJrg5pPbWiAQ "Enable container image scanning using the Aqua Trivy tool.").

*[\>]: and then