---
name: openshift-ts-app-04-timeout-build
title: Why does pushing to the internal registry time out?
description: '[Virtual Private Cloud] [Classic infrastructure]'
last-updated: 2026-02-18
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?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 pushing to the internal registry time out?
{: #ts-app-timeout}
{: troubleshoot}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf}


You try to push an image to the [internal registry](https://cloud.ibm.com/docs/openshift?topic=openshift-registry&format=markdown#openshift_internal_registry), but sporadically you see an error message similar to the following example.
{: tsSymptoms}

```sh
received unexpected HTTP status: 504 Gateway Time-out
```
{: screen}

The default file storage device that provides the storage for the internal registry's images is initially set up with 2 IOPS and 20 GB of storage. When you push larger images, the device might time out because its IOPS is too low to support the image.
{: tsCauses}

[Change the size and IOPS of the existing file storage device](https://cloud.ibm.com/docs/openshift?topic=openshift-file_storage&format=markdown#file_change_storage_configuration).
{: tsResolve}

When you resize the volume in your IBM Cloud infrastructure account, the attached PVC description is not updated. Instead, you can log in to the `openshift-image-registry` (Red Hat OpenShift 4) or `docker-registry` (Red Hat OpenShift 3.11) pod that uses the `registry-backing` PVC to verify that the volume is resized.
{: note}