Requirements
MultiDocker targets macOS. The DNS resolver and TLS trust it configures are macOS-specific; Linux is possible but the DNS setup must be done by hand, and Windows is out of scope.
System
Section titled “System”- macOS (Apple Silicon or Intel).
- A container runtime — OrbStack (recommended) or Docker Desktop.
- Homebrew to install the CLI tools below.
Container runtime: OrbStack vs. Docker Desktop
Section titled “Container runtime: OrbStack vs. Docker Desktop”OrbStack is the recommended runtime. Every container
is automatically reachable from the host at <service>.<project>.orb.local,
which makes database access trivial — no manual
port mapping needed.
Docker Desktop works too, but host DNS into containers is not available. To reach a database from the host you have to map a port temporarily. Everything else behaves the same.
CLI tools
Section titled “CLI tools”MultiDocker relies on a handful of command-line tools:
| Tool | Why it’s needed |
|---|---|
mkcert |
Generates and trusts the local wildcard TLS certificate. |
nss |
Lets mkcert install its CA into Firefox / NSS trust stores. |
yq (mikefarah v4) |
Parses and rewrites compose YAML when rendering overrides. |
jq |
Reads and writes the JSON registry and command output. |
openssl |
Certificate helper used during TLS setup. |
Install them in one go with Homebrew:
brew install mkcert nss yq jqOptional tools
Section titled “Optional tools”cloudflared— only needed for public demo tunnels (mdocker share). Install withbrew install cloudflared.tmux— required for AI terminal sessions.- TablePlus — a nice target for
mdocker db open, but any client works.
Continue to Installation.
Cookie settings
We only use statistics tools if you allow it. Necessary storage keeps this site working; everything else is off until you decide.
Stores your choice from this dialog in your browser (localStorage). No cookie, no transfer to third parties.
Google Analytics 4 via Google Tag Manager, to measure how the site is used. Loaded only after you allow it.