Skip to main content
By the end of this page the daemon runs as a container with durable state and a pinned version — the way to run the server on Windows hosts and on platforms without a native binary.

Run it

State lives in the /data volume; the daemon listens on 0.0.0.0:8137 inside the container, and Docker’s port mapping decides what reaches it. Publish -p 127.0.0.1:8137:8137 to keep it host-local, or -p 8137:8137 to expose it on the host’s interfaces. Pin a version tag for reproducible deployments — tags match the daemon’s released versions:

Compose

Operating a containerized daemon

  • First token: ohd show-token needs the daemon stopped and the same data dir. Stop the container, then run it against the volume:
  • Settings work the same way (stopped daemon, same volume):
  • TLS: the container answers cleartext on its bind; put a TLS-terminating reverse proxy in front for anything beyond a trusted network, exactly as on a native install — see LAN vs TLS proxy.
  • Upgrade: pull the newer tag and recreate the container; state rides the volume. ohd upgrade is for native binaries only.
  • Backup: stop the container and snapshot with the same tooling — see Backup & restore: