---
title: "wendy cloud device cache prune"
description: "Release unused container layer and snapshot caches"
---

## Syntax

```sh
wendy cloud device cache prune [flags]
```

## Examples

```sh
wendy cloud device cache prune --help
```

## Arguments

No positional arguments are declared in the command synopsis.

## Flags

Flags below include inherited options. Types and defaults come from the CLI source. An empty default means no value is configured.

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--all` | bool | `false` | Release every Wendy cache pin regardless of age |
| `--broker-url` | string | (empty) | Tunnel broker host:port (default: cloud :443 endpoint, otherwise <cloud-host>:50052) |
| `--cloud-grpc` | string | (empty) | Cloud gRPC endpoint (optional when a default session is set via 'wendy auth use') |
| `--device` | string | (empty) | Target device hostname; `wendy run` accepts a comma-separated list to deploy one build to several devices (needs a remote build host and --detach). Defaults to $WENDY_DEVICE, then the saved default device |
| `--dry-run` | bool | `false` | Report eligible cache data without releasing it |
| `--json` | bool | `false` | Output in JSON format |
| `--min-age` | string | (empty) | Release cache pins older than this duration (default 24h; minimum 1s) |

## Output

Output depends on the operation and selected target. Use the command help for additional guidance..

## JSON output

The global `--json` option requests machine-readable output. The CLI also selects JSON mode when no interactive terminal is attached. Support and payloads are command-specific; this flag does not guarantee a single JSON document for commands that stream logs or invoke build tools. Consult Details before parsing command output.

## Exit codes

The CLI entry point returns `0` on success and for its user-cancelled or default-cleared results. Other returned errors exit with `1` and print a diagnostic to stderr. Some operations may terminate through subprocess or signal handling; do not infer application health from the CLI exit code alone.

## Common errors

Check argument values and flag combinations against the synopsis above. For discovery, build, port, and readiness failures, see [deployment troubleshooting](../../../../../../errors/). Command-specific constraints are in Details.

## See also

- [wendy cloud device cache](../../../../../../reference/cli/cloud/device/cache/)
- [CLI conventions and configuration](../../../../../../reference/)

## Details

Releases Wendy's cache pins on container layer blobs and unpacked snapshots. With --all, releases every Wendy cache pin immediately (layer blobs and unpacked snapshots) and forces a synchronous containerd garbage-collection pass. By default only pins older than 24h are released; --min-age overrides that and --all releases everything. Apps with a container on the device, running or stopped, keep their layers. Images whose container was deleted lose their unpacked snapshots and are re-unpacked on the next 'wendy run' from the still-cached layer blobs. Apps removed with --cleanup also lose their image, so their layers are re-uploaded on the next run. Do not run --all while a deploy to this device is in progress. --all cannot help when container storage is on the OS root slot (WDY-3127); power-cycle the device instead. Every prune also removes staged chunk uploads left over from earlier deploys and builds, whatever their age, unless a deploy or build used the device's chunk store in the last minute; --dry-run counts them.

Use the command help for additional guidance.