Elyra
 Elyra The coding agent eTerm The terminal that knows where each command ends Huskarl AI colleagues on your own Mac Starf An activity monitor for Apple silicon that never invents a number etrans An SSH and SFTP client for macOS Elyra VM Virtual machines for macOS, Linux and Windows on your Mac Litr A small, native web browser for macOS Notr A notebook for macOS e The native code editor Elyra Grove Native local development environment Askr The real server for Laravel & PHP Elyra Framework Rust + Svelte 5 framework for desktop apps Elyra Conductor Local project conductor Refr Local-first PDF workspace for macOS Elyra Workspace A desktop workspace for coding agents eDock A container runtime for the Mac Elyra SQL Server MySQL-compatible SQL server in Rust Elyra Félagi Agents as teammates on one board Elyra SQL Client Native desktop SQL workbench Elyra SQL Anywhere Replication-ready SQL engine Elyra Sjá SEO & GEO workspace for macOS Elyra DataGrid Server-driven data grid for Laravel
Start here
Getting started
Using Docker
The app
Containers
Images, volumes and networks
Snapshots
Requests
Builds
Linux machines
Kubernetes
Engine and contexts
AI agents
Menu bar
Updates
Reference
Command line
Configuration
Troubleshooting
Under the hood
Architecture
Development
Releasing
Licensing
Release notes
Release notes
Elyra
Elyra
eDock
Snapshots

Snapshots

A snapshot keeps a container's files, or a volume's, as they are now, so you can go back to them. Take one before an upgrade, a migration or anything risky.

Snapshots work on any engine the app shows: eDock, OrbStack, Docker Desktop and the rest.

A container

Snapshot on a container's page takes one, with a note if you like. It's docker commit: an image named edock-snapshots/<container>:<date-time>, of the container's files, with its command and environment.

Its volumes aren't in it. A database's data usually lives in a volume, so snapshot the volume too.

Restore makes the container again from the snapshot, with the same name and settings (ports, mounts, networks, environment, restart policy), and starts it if it was running. The container it replaces is stopped and kept, renamed <name>-before-<date-time>. Remove it once you're happy. A Compose service's container is kept as a snapshot instead (noted Before restoring …), so Compose never sees two of the same service. Volumes, including the anonymous ones an image declares (a database's data), stay with the restored container. If the container is gone, Restore makes a new one from the snapshot, not started, with only what the image keeps (its command and environment, but no published ports or mounts).

A volume

The camera on the Volumes page takes one. It's a .tar.gz of the volume's files, owners and permissions kept, in ~/.edock/snapshots/volumes/<context>/<volume>/ (one folder per engine, so OrbStack's postgres volume and eDock's keep their own) on your Mac. A short-lived alpine container writes it, with no network.

For a database, stop the containers that write to the volume first, as with any copy of its files.

Restore replaces what's in the volume with the snapshot. It's refused while a running container uses the volume, so stop that first. A volume that was removed is made again.

The Snapshots page

Snapshots in the sidebar lists them in two groups, Containers and Volumes, each newest first, with their age, size and note. Each has Restore and Delete.

A container's snapshot is an ordinary image, so it also shows on the Images page, and docker run edock-snapshots/web:20261114-221503 works too.

AI agents

Agents can list snapshots, and take and restore them after you say yes. See AI agents.

Back to docs