---
title: blossom volume:attach
url: "/docs/reference/cli/volume/attach/"
canonical_url: https://docs.blossom88.com/docs/reference/cli/volume/attach/
markdown_url: https://docs.blossom88.com/docs/reference/cli/volume/attach.md
summary: Assign a released Volume to a stopped Service
categories:
- cli
- reference
---

# blossom volume:attach

Assign a released Volume to a stopped Service

## Usage

    blossom volume:attach --id ID --service SERVICE [--mount-path MOUNT_PATH] [--availability AVAILABILITY]

## Flags

| Flag | Description |
| --- | --- |
| `--id (required)` | Volume id |
| `--service (required)` | Stopped Service id in the same Environment |
| `--mount-path` | Container directory (default /data) |
| `--availability` | shared (default) or dedicated Persistent Capacity |

Examples:

    blossom volume:attach --id volume-100 --service service-200 --mount-path /data

Choose a stopped Service without storage in the same Environment and Location.
This assigns the existing disk without starting a Container. Enable it with
`desired_size: 1`, then deploy the Environment. `service:start` can resume a
Service that already has a successful Release. Choose `--availability dedicated`
for its own Server.

To reuse a Volume while creating a Service, set `enabled: false`,
`desired_size: 0`, and `storage.volume_id` in service.yml. Omit `size_gib`.
