Open potchin opened 1 month ago
Not ideal but I managed to get around it by running the migration in a separate container and then copying all the new files back to the pvc inside k8s. There are some hidden files which the app uses to determine the version of the config.
Can you post those files here? and the diff
there was no diff between the config files, that's what was confusing me. Theres a .version
file which needs to contain 0.14
for the migration to be skipped. Not sure what the other files are needed for but I copied them over from another container and it works..
# ls -lrthA
total 1.6M
drwxr-xr-x. 2 root root 4.0K May 25 20:33 model_cache
-rw-r--r--. 1 root root 0 May 25 20:37 backup_config.yaml
-rw-r--r--. 1 root root 8.0K May 25 20:39 backup.db
-rw-r--r--. 1 root root 140K May 25 20:39 frigate.db
-rw-r--r--. 1 root root 17 May 25 20:40 .vacuum
-rw-r--r--. 1 root root 16 May 25 20:40 .timeline
-rw-r--r--. 1 root root 128 May 25 20:40 .jwt_secret
-rw-r--r--. 1 root root 17 May 25 20:40 .exports
-rw-r--r--. 1 root root 4 May 25 20:40 .version
-rwxr-xr-x. 1 root root 0 May 25 20:40 config.yml
-rw-r--r--. 1 root root 32K May 25 20:57 frigate.db-shm
-rw-r--r--. 1 root root 1.4M May 25 20:57 frigate.db-wal
# cat .version
0.14
yeah i can see i dont have version file in mine and it can write all files in /config beside config.yml :-D
so basicly could be solved by adding to values. versionsfile: enabled: true version: 0.14
that makes that file?
ah reading hes changes, i can see he have changes to mask coordinates etc. so i will be hit by it
It looks as though having the frigate
config.yml
stored inside a configmap causes a problem for frigate 0.14.0-beta1 since it tries to make changes to the config file. This fails since its readonly..I've tried running frigate separately to generate an updated config file (which is no different)