> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/data-flows/services/service-resources-view/volumes-view.md).

# Volumes View

Check the persistent storage volumes that your services use in Docker Compose deployments of Connectware.

Volumes provide persistent storage for services. The overview page displays information about the associated service, the volume name ([resource ID](/2-6-1/data-flows/service-commissioning-files/resources.md#resource-id)), creation date and time, and current status.

See also: [Cybus::Volume resource](/2-6-1/data-flows/service-commissioning-files/resources/cybus-volume.md)

{% hint style="info" %}
This feature is available only for Docker Compose deployments of Connectware. It is not supported on Kubernetes.
{% endhint %}

## Overview

<figure><img src="https://2858848828-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F38tgcn74JQcOsNlglPZq%2Fuploads%2Fgit-blob-7e8cc97cb4154737b7f587755fbe6ba0a59a629b%2Fvolumes_overview.png?alt=media" alt=""><figcaption></figcaption></figure>

Clicking on a listed volume redirects you to the [Volume Details View](#volume-details-view) for that volume.

## Volume Details View

Each volume has its own resources. For a selected volume, the **Volume Logs** and **Labels** tabs are available.

<figure><img src="https://2858848828-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F38tgcn74JQcOsNlglPZq%2Fuploads%2Fgit-blob-dde25cd50ba48b7fde48ae54713fb64ac75f4888%2Fvolumes_details_open.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/data-flows/services/service-resources-view/volumes-view.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.