-
Notifications
You must be signed in to change notification settings - Fork 81
Open
Description
It looks like there's something with the default yaml that prevents loading for the config migration. Even when I delete all config values it doesn't seem to want to load/migrate.
2025-02-09 00:29:02.829270387 00:29:02.829 INF [webrtc] listen addr=:8555/tcp │
│ 2025-02-09 00:29:04.650418239 [2025-02-09 00:29:04] frigate.util.config INFO : Checking if frigate config needs migration... │
│ 2025-02-09 00:29:04.651111972 ************************************************************* │
│ 2025-02-09 00:29:04.651114165 ************************************************************* │
│ 2025-02-09 00:29:04.651153760 [2025-02-09 00:29:04] frigate.util.config ERROR : Failed to load config at /config/config.yml │
│ 2025-02-09 00:29:04.651165124 *** Your config file is not valid! *** │
│ 2025-02-09 00:29:04.651168873 *** Please check the docs at *** │
│ 2025-02-09 00:29:04.651169953 *** https://docs.frigate.video/configuration/ *** │
│ 2025-02-09 00:29:04.651170965 ************************************************************* │
│ 2025-02-09 00:29:04.651176366 ************************************************************* │
│ 2025-02-09 00:29:04.651177824 *** Config Validation Errors *** │
│ 2025-02-09 00:29:04.651179277 ************************************************************* │
│ 2025-02-09 00:29:04.651196991 : Input should be a valid dictionary or instance of FrigateConfig │
│ 2025-02-09 00:29:04.651198877 ************************************************************* │
│ 2025-02-09 00:29:04.651200365 *** End Config Validation Errors *** │
│ 2025-02-09 00:29:04.651201895 ************************************************************* │
│ 2025-02-09 00:29:04.933702332 [INFO] Service Frigate exited with code 1 (by signal 0) │
│ s6-rc: info: service legacy-services: stopping
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels