Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config file is read-only, unable to migrate config file. #78

Open
XDDK opened this issue Nov 4, 2024 · 5 comments
Open

Config file is read-only, unable to migrate config file. #78

XDDK opened this issue Nov 4, 2024 · 5 comments

Comments

@XDDK
Copy link

XDDK commented Nov 4, 2024

I've tried everything in the world to make the config file not read-only so that it's editable from the UI. How can I fix this?

tried with full rights to the container, giving exisiting pvc, no pvc defaulting to emptyDir and nothing worked.

securityContext:
  runAsNonRoot: false
  privileged: true
  runAsUser: 0
  runAsGroup: 0
@apetrycki
Copy link

I have the same question. I have a persistent store and would like an option to not have the config stored in the ConfigMap and instead read from the persistent store.

@amorabito
Copy link

Yes i think main issue is that it is hardcoded as the ConfigMap mounted to where frigate reads from, so no way to mount it as rw.
Maybe if you could change location where frigate loads config from (i am very new to frigate) and create a custom Dockerfile to copy from ConfigMap mount location to that PVC location.

@newbenji
Copy link

newbenji commented Nov 28, 2024

Create init container,. move mount of config file so init container copy it there on start
evt make this default, but option to do it

@amorabito
Copy link

Yes having ability to define an initcontainer would be nice

@aaronspruit
Copy link

I'd love to see this PR get committed - #79. I've recently setup frigate with helm and there's no "easy" way to make camera masks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants