---
name: Registry-ts_image_timeout
title: Why does it time out when I list images in Container Registry?
description: Listing images times out in IBM Cloud&reg; Container Registry. You can resolve image list timeouts in Container Registry by restricting the scope of the list or by disabling vulnerability reports.
last-updated: 2026-08-03
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/Registry?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why does it time out when I list images in Container Registry?
{: #troubleshoot-image-timeout}
{: troubleshoot}
{: support}

Listing images times out in IBM Cloud&reg; Container Registry. You can resolve image list timeouts in Container Registry by restricting the scope of the list or by disabling vulnerability reports.
{: shortdesc}

The request timed out while you attempted to list your images in the IBM Cloud console, command-line interface (CLI), or API.
{: tsSymptoms}

The most likely cause of the timeout is that the account has many images. The vulnerability reports can't be displayed because the targeted account contains more images than Vulnerability Advisor can process.
{: tsCauses}

You can run the [`ibmcloud cr image-list`](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcli&format=markdown#bx_cr_image_list) command with the `--restrict` option to reduce the scope of the list and increase performance. Alternatively, if you don't want to fetch vulnerability reports, use the `--no-va` option. For help with managing the number of images, see [Cleaning up your namespaces](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention&format=markdown).
{: tsResolve}