Getting started

August 7, 2026 · View on GitHub

← Manual index

First run

  1. Start the binary (./dockercmd) and open http://127.0.0.1:8470.
  2. Create the admin account — the first account is always an admin. On the same screen you choose whether to enable 2FA now or skip it for now (leaving localhost password-only — handy for a local/dev box).
  3. If you enable 2FA — scan the QR code with an authenticator app (Google Authenticator, Aegis, 1Password…) and enter the 6-digit code to confirm. You can change the localhost exemption later (see Settings).

After that you log in with username + password + the current TOTP code.

Sign in

A passkey is the other kind of second factor, paired later from Profile → Security. Where the account has one, the second step offers it beside the code box; where the account has only a passkey, the code box is not shown at all, because asking for a code it cannot produce would be a dead end.

Two-factor step

The layout

  • A left sidebar groups the agendas (Compute, Network, Observability, System). What you see depends on your role and permissions.
  • A host switcher appears at the top of the sidebar once more than one host is configured — it rebinds every view to the selected Docker host.
  • The account menu (bottom-left) shows who you are and signs you out.

Day-to-day basics

  • The Dashboard is the home view: host facts, disk usage, and the running containers.
  • Containers is where you operate workloads — start/stop, open a shell, browse files, read logs.
  • Set up Alerts so problems reach you by webhook or email even when no one is watching the UI (the server monitors 24/7).

Security model in one minute

  • Passwords are hashed with Argon2id; sessions are HttpOnly cookies.
  • A second factor is enforced for everyone unless an admin enables the localhost exemption. That can be an authenticator app (TOTP) or a passkey — an account may hold several of either, and the last one cannot be removed.
  • A passkey that verifies you with a PIN, fingerprint or face can also sign you in on its own, once you turn that on per account. Your password keeps working: it is the way back if the key is lost, since no admin can reset another account's second factor. See Your profile.
  • Account type: admin (full access + administration) or user. A user reaches only what they are granted — through named roles (a reusable bundle of sections, each read or write, optionally limited to specific hosts) and/or sections set directly on the account.
  • Stored secrets (registry / SMTP / LDAP passwords) are encrypted at rest.

See Users & roles and Settings for administration.