Engine support
Oxidock works with Docker-compatible engines by reading the active provider and routing operations through supported Docker APIs and command workflows.
Supported providers
| Provider | Status | Notes |
|---|---|---|
| Docker Desktop | Supported | Good default for most Docker users. |
| OrbStack | Supported | Fast local development engine on macOS. |
| Colima | Supported | Lightweight local Docker-compatible VM. |
| Rancher Desktop | Supported | Useful when Kubernetes workflows are nearby. |
| Local Docker | Supported | Works when the local socket and context are available. |
| Remote contexts | Supported | Depends on your Docker context configuration. |
Provider switching
Engine provider switching lets you move between local and remote contexts without treating Oxidock as a cloud control plane. The active provider determines which resources appear and which commands are available.
Troubleshooting
If an engine does not appear:
- Start the engine outside Oxidock first.
- Verify
docker context lsshows the expected context. - Check socket permissions.
- Restart Oxidock after changing provider settings.
Oxidock does not replace your engine. It gives you a focused UI and learning layer on top of Docker-compatible providers.