0 Try the Demo

Volumes

Create, rename, edit, back up, and remove Docker volumes.

Docker volumes hold data that outlives a container, such as databases and uploads. The Volumes page lets you create, rename, and remove volumes, edit the files inside them, and back them up.

See which volumes are in use and how much data they hold.

Browse volumes

Open Volumes in the sidebar. The table shows name, driver, and current usage for each volume.

Create a volume

  1. Click Create Volume.
  2. Enter a name.
  3. Optional: pick a driver or add labels.
  4. Click Create.

Remove a volume

  1. Open the row’s dropdown and click the trash icon.
  2. Confirm.
Note

Volumes used by a container can’t be removed.

Rename a volume

A volume that is not in use by any container can be renamed from its row dropdown. Arcane copies the volume data to a volume with the new name, then removes the original.

Note

Renaming a volume that a project manages doesn’t update the project. Change the volume name in the project’s configuration too, or the next deploy may recreate the original volume.

Volume Workspace

Open a volume’s Workspace to work with its files while containers keep running:

  • Open any UTF-8 text file in a tab and edit it.
  • New File and New Folder create files and folders anywhere in the volume.
  • Upload Files adds files from your computer and asks before replacing existing ones.
  • Download saves any file, including binary files, to your computer.
  • Rename, Move, and Delete reorganize the contents.
  • Restore a single file from an existing volume backup instead of restoring the whole volume.
Browse and edit files in a volume while its container keeps running.

If the container sets a numeric user:, workspace writes use that user and group instead of root.

Edits are staged locally and applied together when you Save. If someone else changed the volume in the meantime, the save is rejected with “Volume workspace changed; refresh it and try again” — refresh and reapply.

  • Binary files, symlinks, and special files are read-only in the editor; binary files can still be uploaded, downloaded, and moved.
  • Files larger than the configured maximum (default 10 MiB) can’t be edited in place.
  • Very deep or very large trees are truncated by the configured depth and entry limits, and the workspace tells you when that happens.
  • Volumes that use a custom mount configuration (bind-style driver options) can’t be opened in the workspace.

The size and tree limits are configurable with the VOLUME_WORKSPACE_MAX_FILE_SIZE_MB (default 10), VOLUME_WORKSPACE_MAX_DEPTH (default 50), and VOLUME_WORKSPACE_MAX_ENTRIES (default 10000) environment variables.

Browsing and downloading need volumes:read; which write actions need which permission is listed in the permission catalog.

Note

Existing roles and API keys with the legacy volumes:browse permission are migrated to volumes:read automatically.

Back up and restore

Open a volume’s Backups to create or schedule snapshots on local storage or S3, or to restore data. Backups covers setup and recovery, and System-managed volume backups covers scheduling several volumes together.

Helper containers

Arcane creates helper containers for backup, restore, and workspace access. They carry the label com.getarcaneapp.internal.resource=true and are hidden from the Containers list by default. Turn on Show Internal Containers in the container table’s view options to see them.

Backups and restores run in short-lived containers using Rustic, the backup tool behind Backups. The workspace helper keeps the volume mounted between operations so it doesn’t need to start again each time you browse. Arcane removes it after the Volume Helper Idle Timeout, which defaults to 10 minutes. Set it to 0 to disable idle cleanup.