---
name: containers-ts-storage-block-not-attached
title: Why do I get a `Volume not attached` error when trying to expand a Block Storage for VPC volume?
description: '[Virtual Private Cloud]'
last-updated: 2026-04-10
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/containers?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 do I get a `Volume not attached` error when trying to expand a Block Storage for VPC volume?
{: #block_not_attached_vpc}
{: support}

[Virtual Private Cloud]{: tag-vpc} 


When you edit a Block Storage for VPC and update the `spec.resources.requests.storage` section to expand your volume, you see the following error:
{: tsSymptoms}

```sh
Volume not attached
```
{: screen}


You tried to expand the volume size of an existing Block Storage for VPC PVC that is not mounted by a pod. Only volumes mounted by app pods can be expanded.
{: tsCauses}


Verify that your PVC supports volume expansion, then create an app pod that uses your PVC.
{: tsResolve}

1. Describe your existing PVC and verify that `allowVolumeExpansion` is set to `true`.

    ```sh
    kubectl describe pvc <pvc-name>
    ```
    {: pre}

1. Create an app pod that uses your PVC and deploy it to your cluster.

1. Edit the PVC and increase the value in the `spec.resources.requests.storage` field.

    ```sh
    kubectl edit pvc <pvc-name>
    ```
    {: pre}

1. Get the details of your PVC and make a note of the PV name.

    ```sh
    kubectl get pvc <pvc-name>
    ```
    {: pre}

1. Describe your PV and make a note of the volume ID.

    ```sh
    kubectl describe PV
    ```
    {: pre}

1. Get the details of your Block Storage for VPC volume and verify the capacity.

    ```sh
    ibmcloud is vol <volume-ID>
    ```
    {: pre}