Hi,
I installed vikunja on my microk8s, but from version 0.20.3 (API container, and with 0.20.4 too) I have a problem:
info: creating the new user vikunja with 1000:1000
usermod: no changes
chown: ./config.yml: Read-only file system
this is because I have the config.yml in a configmap.
I can use an init container to copy the config file to a RW filesystem, however if the file is edited by vikunja, this may cause an issue.
Do you have any thoughts about how to resolve this?
Where are you mounting the config file? It should work if you put it in /etc/vikunja/config.yml.
We also have a helm chart now, feel free to take that for a spin: vikunja/helm-chart - helm-chart - Gitea
On another note, the docker container should not try to chown the config file.
Ok thank you!
I was mounting the configuration in /app/vikunja/config.yml
I will use the helm chart in the future.
Thank you so much for your prompt response (and for vikunja!).
Pls how did you resolve this, im having the same issue in my kind and eks cluster.
➜ vikunja-0-4-1 k logs my-vikunja-api-667d55b4cc-5vswh
info: creating the new user vikunja with 1000:1000
usermod: no changes
2023/12/03 21:38:13 Using config file: /etc/vikunja/config.yml
2023-12-03T21:38:13.966972083Z: CRITICAL 
migration/Migrate 002 Migration failed: dial tcp [::1]:5432: connect: connection refused