Where Does Yacht Store Config and Database?
Where Yacht keeps its config volume, database and templates.
Last updated
Yacht follows single volume conventions: a /config mount holding the SQLite database, settings and templates cache. The compose file beside it records ports and mounts.
Deprecation matters here: upstream archived Yacht, so pin working images and keep local backups independent of registries. Confirm filenames by listing /config on your install before scripting around them.
Where Yacht stores this, by platform
<yacht config>/yacht.db
/config mount with database, settings and templates. Upstream is archived, so pin images and keep local backups. Verify filenames by listing the volume.
Frequently asked questions
Yacht forgot everything after updating. Why?
Persist /config as a volume. The database plus settings live inside it, so unmounted containers reset to first boot on every recreate.
What must I back up for Yacht?
Back up the /config tree (database plus settings) and the compose file together. Templates refresh from upstream, but your stacks and users ride in the volume.
Notice an outdated path? Let us know.