Where Does Kometa Store Its Config?
Kometa reads config.yml from a /config volume for Plex connections, libraries, and overlays. Lose that folder, lose everything.
Last updated
Kometa stores its state in a config tree mounted at /config in Docker. The one required file is config.yml, which holds the Plex URL and token plus global library settings and service keys. Collection files, overlay files, and metadata files live beside it in the same tree.
The whole folder moves as one unit. Migrations fail when people copy config.yml alone and leave the collection files behind, which produces run errors about missing paths. Stop the container, copy everything, mount it at /config on the new host. Host paths inside the YAML must match between machines or Kometa will not find its own files.
Where Kometa stores this, by platform
/config/config.yml (Docker volume)
config.yml holds Plex credentials, library blocks, and service keys. Collection, overlay, playlist, and metadata YAML files sit beside it. Bind this tree to a host folder; the container side is always /config.
Frequently asked questions
how do i migrate kometa to a new server
Stop the container and copy the whole mapped /config folder (config.yml plus collection, overlay, and metadata files). Restore by mounting it at /config on the new host. The Plex token travels inside config.yml, so treat the copy as secrets.
kometa created a config.yml.template instead of config.yml
Kometa downloads a template config.yml.template when no config.yml exists. Copy it to config.yml and fill in the Plex URL, token, and TMDb key. The template is only a starting point and will not run until you edit it.
Notice an outdated path? Let us know.