setup & Infrastructure
These verbs provision and verify the shared infrastructure. Run setup
once after installation; the individual phases exist for re-running a single part.
Full first-run install. Runs all phases in order.
mdocker setup| Aspect | Detail |
|---|---|
| Args / flags | — |
| Calls | setup-network.sh, setup-tls.sh, setup-dns.sh, then edge up. |
| Side effects | Creates ~/.config/multi-docker/, certificates, the resolver and the edge containers. Prompts for sudo once (for the resolver). |
setup-tls
Section titled “setup-tls”(Re-)generate the wildcard certificate and install the mkcert CA.
mdocker setup-tlsWrites wildcard.pem and wildcard-key.pem under the cert store and installs the
mkcert CA.
setup-dns
Section titled “setup-dns”Write the macOS resolver for the base domain.
mdocker setup-dnsWrites /etc/resolver/<base-domain> (requires sudo).
setup-network
Section titled “setup-network”Create the shared Docker network.
mdocker setup-networkCreates the multi-docker-edge Docker network.
setup-admin
Section titled “setup-admin”A bundle of the admin-privileged phases (setup-tls + setup-dns), designed for the
macOS app’s AppleScript admin escalation.
mdocker setup-admindoctor
Section titled “doctor”Read-only health check of the toolchain and state.
mdocker doctorChecks the required tools, the mkcert CA, the resolver, the edge network and ports
80/443. See Running mdocker doctor.
Related
Section titled “Related”- First-Run Setup
- Concept: DNS & TLS
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.