Docker operations
You can run Pulse in Docker with the published image or by building from local source. Use Docker when you want a repeatable runtime and persistent /data volume.
Published image vs build from source
Volume strategy
Persist /data. It holds SQLite, uploads, board graphs, global discovery, and MCP traces.
Environment variable overrides for production
Inside containers, bind both API and MCP to all interfaces:
Multi-container setups
The community image defaults to local SQLite and embedded LadybugDB files. If you move supporting services out of the container, keep Pulse single-process for the API/UI and MCP servers so shared state and the embedded graph writer stay coherent.
Logs and debugging
Upgrading
For minor releases, pull the new image and restart against the same volume. Check the upgrade guide when a release notes a schema migration.
Related pages
Last modified on May 8, 2026
