App push on Diego cells not working in Tanzu Platform - Cloud Foundry

Products

• VMware Tanzu Platform - Cloud Foundry

Issue/Introduction

When you do a cf push you would see the operation failing with an error similar to the below snippet:

25-11-10T11:06:22.184+05:30 [STG/0] [OUT] Cell a5412c34-df56-4b11-872c-0b3ffebca733 destroying container for instance bdfd0d72-072a-4cd7-8bd1-0c3263c9cfdc
2025-11-10T11:06:22.185+05:30 [STG/0] [OUT] Cell a5412c34-df56-4b11-872c-0b3ffebca733 successfully destroyed container for instance bdfd0d72-072a-4cd7-8bd1-0c3263c9cfdc
2025-11-10T11:06:42.860+05:30 [STG/0] [OUT] Downloading java_buildpack_offline...
2025-11-10T11:06:52.137+05:30 [STG/0] [OUT] Downloading java_buildpack_offline failed
2025-11-10T11:06:52.154+05:30 [STG/0] [OUT] Cell 251ec905-359b-47b6-9f39-2aea34ce3793 destroying container for instance bdfd0d72-072a-4cd7-8bd1-0c3263c9cfdc
2025-11-10T11:06:52.155+05:30 [STG/0] [OUT] Cell 251ec905-359b-47b6-9f39-2aea34ce3793 successfully destroyed container for instance bdfd0d72-072a-4cd7-8bd1-0c3263c9cfdc
2025-11-10T11:07:12.967+05:30 [STG/0] [OUT] Downloading java_buildpack_offline...
2025-11-10T11:07:22.509+05:30 [STG/0] [OUT] Downloading java_buildpack_offline failed
2025-11-10T11:07:22.535+05:30 [STG/0] [OUT] Cell aca10e5f-cdbc-467e-b078-d96d0bf304f2 destroying container for instance bdfd0d72-072a-4cd7-8bd1-0c3263c9cfdc
2025-11-10T11:07:22.536+05:30 [STG/0] [OUT] Cell aca10e5f-cdbc-467e-b078-d96d0bf304f2 successfully destroyed container for instance bdfd0d72-072a-4cd7-8bd1-0c3263c9cfdc
2025-11-10T11:07:22.584+05:30 [API/1] [ERR] Failed to stage build: staging failed

 

Cause

There could be many possible issues related to this error ranging from buildpack issues to linux stack, cell resources and other issues.

You can start by checking the rep logs on the corresponding Diego cells and this KB covers one such possibility which is Blobstore running out of storage space.

{"timestamp":"2025-11-10T06:59:07.088024108Z","level":"error","source":"rep","message":"rep.executing-container-operation.task-processor.run-container.containerstore-create.node-create.failed-fetching-cache-dependency","data":{"cache-key":"eb6782c6-87b6-49c8-888b-1f0ed3b287e0_485041a0d9d79e1e043637a62fbf2c80b778a50dc780a27ff84a882a04e1f984","container-guid":"d6474394-d199-4c3c-a617-584cfe557f08","container-state":"reserved","download-url":"https://blobstore.service.cf.internal:4443/read/cc-buildpacks/eb/67/eb6782c6-87b6-49c8-888b-1f0ed3b287e0_485041a0d9d79e1e043637a62fbf2c80b778a50dc780a27ff84a882a04e1f984?md5=wu4wdtgt8ge82uuCnqTNuQ\u0026expires=1762761466","error":"write /var/vcap/data/rep/shared/garden/download_cache/temp/c5cdb6274ec56994a6e460bd1df39a82-1966656722: no space left on device","guid":"d6474394-d199-4c3c-a617-584cfe557f08","session":"127844.1.3.2.1"}}

 

Resolution

Depending on whether the Blobstore is internal or external you can increase the storage space accordingly, if its internal (i.e webdav) you can increase the storage of the blobstore VM from the Resource config section in the TAS/EAR tile accordingly.