Overview
Oxy requires a Docker API-compatible endpoint to manage PostgreSQL, ClickHouse, and other containerized services. This means any container runtime that exposes a Docker-compatible API socket.Key Takeaway
TL;DR: Oxy needs a Docker API-compatible socket endpoint, not a specific application.You can use:
- Docker Engine installed directly (no GUI)
- Docker Desktop, Rancher Desktop (with dockerd/moby), Colima, OrbStack, etc. (with GUI)
- Podman with Docker socket emulation
What Oxy Actually Needs
Container Runtime
Docker Engine (dockerd) or any Docker API-compatible runtimeThis is the actual runtime that manages containers
Docker-Compatible API Socket
A Docker API endpoint at:
unix:///var/run/docker.sock(default on Linux/macOS)npipe:////./pipe/docker_engine(Windows)- Custom location via
DOCKER_HOSTenv var
The applications listed below (Docker Desktop, Rancher Desktop, etc.) are just convenient ways to install and manage the underlying container engine. You can also install Docker Engine directly without any desktop application - see the “Docker Engine (Standalone)” tab.
Installation Options
You can install a Docker-compatible container engine in several ways:Installation & Setup
- Docker Engine (Standalone)
- Docker Desktop
- Rancher Desktop
- Colima (macOS)
- Podman
- OrbStack (macOS)
Install Docker Engine Only (No Desktop App)
This installs just the Docker Engine (dockerd) without any GUI application. Perfect for servers or if you prefer a lightweight setup.
Custom Docker Host
For non-standard socket locations or remote Docker hosts, set theDOCKER_HOST environment variable before running Oxy. This is the standard Docker environment variable that Oxy (and the Docker CLI) automatically respects.
Setting DOCKER_HOST
~/.bashrc, ~/.zshrc, etc.) to make it permanent.
Common Socket Locations
| Runtime | Default Socket Location |
|---|---|
| Docker Desktop | unix:///var/run/docker.sock (macOS/Linux) |
npipe:////./pipe/docker_engine (Windows) | |
| Rancher Desktop | unix://$HOME/.rd/docker.sock (macOS) |
unix:///var/run/docker.sock (Linux) | |
| Colima | unix://$HOME/.colima/default/docker.sock |
| Podman | unix://$XDG_RUNTIME_DIR/podman/podman.sock |
| OrbStack | unix://$HOME/.orbstack/run/docker.sock |
Troubleshooting
Failed to connect to container runtime
Failed to connect to container runtime
Check if runtime is running:Common solutions:
- Start your container runtime application
- Wait 30-60 seconds for full initialization
- Verify Docker CLI works:
docker ps - Check DOCKER_HOST environment variable:
Rancher Desktop: daemon not responding
Rancher Desktop: daemon not responding
- Open Rancher Desktop preferences
- Switch Container Engine to dockerd (moby)
- Restart Rancher Desktop
- Wait for full initialization (30-60 seconds)
- Retry:
oxy start
Colima: connection refused
Colima: connection refused
Podman: no such file or directory
Podman: no such file or directory
Enable Docker socket compatibility:Linux:For Podman Desktop, enable Docker compatibility in settings.
Permission Denied (Linux)
Permission Denied (Linux)
Add your user to the docker group:Then verify:
Enterprise Mode Containers
When using the--enterprise flag, Oxy starts additional containers:
PostgreSQL
Main databasePort:
15432ClickHouse
Analytics databasePorts:
8123 (HTTP), 9000 (Native)OpenTelemetry Collector
Observability pipelinePorts:
4317 (gRPC), 4318 (HTTP)Cube.js
Semantic layerPort:
4000Performance Considerations
macOS Performance Comparison
Different runtimes have varying performance characteristics on macOS:OrbStack
Fastest - Lowest resource usage, native performance
Colima
Fast - Good performance, lightweight footprint
Docker Desktop
Good - Excellent compatibility, higher resource usage
Rancher Desktop
Good - Rich features, moderate resource usage
On Linux, all runtimes perform similarly as they use native kernel features.
On Windows, Docker Desktop offers the best support and performance with WSL2 integration.
Clean Start
Remove all Oxy containers and volumes for a fresh start:- All Oxy-managed containers
- Associated volumes
- Container networks (enterprise mode)