Install Orca
Download Orca Desktop for macOS, Windows or Linux, let it set up a container runtime on first start, and keep it up to date.
On this page
This page covers installing Orca Desktop, what it sets up the first time you start it, how updates work, and how to remove it. If you want to manage a Linux server instead of your own machine, see Install the daemon on a server.
Download
Get the latest release from GitHub: github.com/edvin/orca/releases/latest.
| Platform | File | What it is |
|---|---|---|
| macOS (Apple Silicon) | .dmg | Disk image with the signed and notarized app. Drag Orca Desktop to Applications. |
| Windows (x64) | -setup.exe | Installer. It also adds the install folder to your user PATH, so the orca CLI works in any new terminal. |
| Linux (x86_64) | .AppImage | Portable app. Make it executable and run it. |
| Linux (x86_64) | .deb | Package for Debian and Ubuntu. It depends on libwebkit2gtk-4.1-0 and libssl3. |
Each download bundles the Orca daemon (orca-daemon) and the orca CLI. The app starts the daemon for you and stops it when you quit.
Release builds of the desktop app are made for Apple Silicon Macs, x64 Windows and x86_64 Linux. There is no Intel Mac build.
First start
When Orca starts, it looks for a working container runtime. If it finds one, you go straight to the app. If not, it opens System Health with a Container runtime setup list: each missing piece has an Install button, and the setup log streams in a dialog while it runs.
macOS
Orca runs Docker in a small Linux VM managed by Lima. Setup does this, in five steps:
- Installs Homebrew if it's missing.
- Installs Lima, the Docker CLI, Docker Compose and Docker Buildx with Homebrew (only the ones you don't have). Lima older than 2.0 is upgraded.
- Creates a VM named
orcaon Ubuntu 26.04 LTS using Apple's Virtualization.framework. The first time this downloads the Linux image and takes a few minutes. - Starts the VM and checks that it is reachable.
- Creates a Docker context named
lima-orcaand switches to it, so thedockercommand in your terminal talks to the same engine as Orca.
The VM gets 4 CPUs and memory sized from your Mac: half of its RAM, between 4 and 16 GiB, always leaving at least 2 GiB for macOS. You can change this later. See How Orca runs on macOS.
Windows
Orca runs Docker inside WSL2.
- If WSL2 is not active, the WSL2 check offers to install it (
wsl --install). You may need to restart Windows afterwards. - Orca uses your default WSL distro. If you don't have one, install Ubuntu from the Microsoft Store and launch it once to create your Linux user.
- The Docker Runtime step installs Docker in that distro with the official script from get.docker.com, adds your Linux user to the
dockergroup, and makes Docker listen on127.0.0.1:2375so Orca can reach it from Windows.
Linux
Orca talks to Docker or Podman on your machine directly, with no VM.
- If no runtime is found, the Docker Runtime step runs the get.docker.com script with
sudo, adds you to thedockergroup and starts the service. Ifsudoasks for a password, Orca can't type it for you: the dialog prints the commands to run in a terminal instead. - If Docker isn't installed, System Health also offers Podman as an alternative.
- After being added to the
dockergroup, log out and back in for it to take effect.
Requirements
What the release builds and setup need:
- macOS: an Apple Silicon Mac. Setup installs Homebrew and Lima 2.0 or newer, and needs internet access to download them and the Ubuntu image.
- Windows: x64 Windows with WSL2 and a WSL Linux distro.
- Linux: x86_64 with WebKitGTK 4.1, plus Docker or Podman (Orca can install either).
Next to Docker Desktop
You don't have to uninstall Docker Desktop first.
- macOS: if Docker Desktop's engine is the active Docker context, Orca connects to it. System Health then shows a Switch to Orca runtime card. Switch to Orca runtime sets up the Lima VM if needed, switches the Docker context to
lima-orcaand restarts the Orca daemon. Tick Also stop Docker Desktop to free resources to quit Docker Desktop at the same time. Images and containers from Docker Desktop are not copied into the VM: you pull or rebuild them there. - Windows: Orca connects to Docker Desktop's engine when it is running, and otherwise to Docker in WSL2.
- Linux: Orca uses the first runtime socket that responds, starting with
DOCKER_HOSTand the active Docker context.
Updates
Orca checks for a new version 5 seconds after it starts and then every hour. When one is available, the status bar at the bottom shows Update available: v…. Click it, confirm with Update, and Orca downloads the release, stops its daemon, installs the update and restarts. Updates are signed, and the app verifies the signature before installing.
Settings > Privacy & security > Network connections lists the update check along with every other connection Orca makes.
Uninstall
First quit Orca from the tray or menu bar icon with Quit Orca. Closing the window only hides it.
macOS
- Delete Orca Desktop from Applications.
- To remove the VM and everything in it, run:Terminal
limactl stop orca limactl delete orca - Point the Docker CLI back at another engine, and remove Orca's context:Terminal
docker context use default docker context rm lima-orca - Delete
~/Library/Application Support/orcato remove settings, the API token and the local CA.
You can do steps 2 and 4 from the app before you quit it, in Settings > About > Cleanup: Stop & remove VMs stops and deletes the orca VM, and Reset all also deletes the settings folder. Other Lima VMs on the Mac are left alone.
Homebrew and the packages setup installed (lima, docker, docker-compose, docker-buildx) stay. Remove them with brew uninstall if you don't need them.
Windows
Uninstall Orca Desktop from Settings > Apps in Windows. The uninstaller removes the orca:// link handler, its PATH entry, %LOCALAPPDATA%\orca, and the Docker TCP listener it added in WSL. It keeps your settings in %APPDATA%\orca; delete that folder to remove them too. Docker stays installed in your WSL distro.
Linux
Delete the AppImage, or remove the .deb package with your package manager. Then delete ~/.config/orca (settings, API token, CA) and ~/.local/share/orca if you want a clean slate. Docker or Podman stay installed.
On every platform the gateway runs as a container named orca-gateway. Remove it with docker rm -f orca-gateway if it's still there.
Install the daemon on a server
To manage a Linux server from Orca Desktop, install only the daemon there. On Debian or Ubuntu:
curl -fsSL https://orca-desktop.com/install-daemon.sh | sudo shIt adds Orca's apt repository, installs orca-daemon as a systemd service and prints the URL and API token to paste into Settings > Remote hosts. To remove it:
curl -fsSL https://orca-desktop.com/uninstall-daemon.sh | sudo shSee Remote hosts for connecting to it and putting TLS in front.
Next steps
- Quickstart: open a project folder and give it an HTTPS hostname.
- How Orca runs on each platform
- Troubleshooting