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
Updates

Updates

eDock checks for a new version each time it starts. Choose Check for Updates… in the menu bar item's menu to check at any other time. Check for updates on the Engine page and in the ⌘K palette do the same.

Installing an update

When there's a newer version, a notice in the window offers it:

  1. ↑ Update available: v0.3.0, with What's new to read the release notes, Install and Later.
  2. Install downloads and checks the update, showing its progress.
  3. v0.3.0 is installed. Restart to use it. Restart opens the new version now. Later leaves it for the next time you open eDock. Nothing restarts until you say so.

eDock replaces itself only in a folder you can write to, normally Applications. See Troubleshooting if installing refuses.

Then restart the engine

The engine that was running keeps running the previous version, so your containers aren't interrupted by the update. The Engine page notices and offers Restart engine. Press it when it suits you. Running containers stop and start again, and an engine you'd stopped stays stopped.

How an update is checked

An update is installed only if all of these hold:

  • Its signature. The download is signed with eDock's update key, and eDock carries the public half of that key.
  • Its checksum. The download matches the SHA-256 the release lists.
  • Its Developer ID. The app inside is signed with eDock's Apple Developer ID for this app, and is unaltered since it was signed.
  • It's newer. It's a newer version than the one running. An older release is never offered.

If any check fails, nothing is installed and the running eDock is left as it was.

The check asks GitHub for the newest release's latest.json over HTTPS, straight from the app. It doesn't use the engine's proxy setting, so on a network that only lets traffic out through a proxy, the check fails and eDock stays as it is. Nothing about you or your containers is sent.

Back to docs