So all the problems were related to using a different DB schema.
I just deleted the following part form my values.yml file and everything is working now:
statefulset:
env:
-…As my other tickets described, it is not a good idea to use a different DB schema.
I just deleted the following part form my values.yml file and everything is working now:
statefulset:
…I could fix the problem by the help of @zeripath explanation from: https://github.com/go-gitea/gitea/issues/16961#issuecomment-914580867
I could fix the problem... In short it is not a good idea to use a different DB schema...
After I removed the following part:
statefulset:
env:
- name: GITEA__DATABASE__SCHEMA
…Hi, I'm running gitea on my RPi 4 with plain kubernetes... Everything you need to add is:
postgresql:
image:
repository: postgres
tag: 11.9
pullPolicy: IfNotPresent
…Yes I tried it but didn't worked. I'm getting the message that username or password is wrong.
I think it has to do something with the problem from gitea/helm-chart#216 I…
See below some outputs from the database:
$ kubectl exec -it -n gitea gitea-postgresql-0 -- bash
Defaulted container "gitea-postgresql" out of: gitea-postgresql, init-chmod-data…@zeripath maybe you remember that we discussed this via discord nearly 4 months ago. At this time I migrated from sqlite to postgresql and had exactly the same issue, we had a discussion in private…
Some months ago I did a migration from sqlite to postgresql with the version: xorm/xorm#1906 Maybe this helps for identifying the problem.
Yes I need to use this image because the default one from you doesn't work for me on a RPi 4.
I'm trying this with complete fresh folder. So there is no pre-existing db at the claim.
See below my values.yaml file:
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
privileged: false
runAsGroup: 1000
runAsNonRoot: true
…See below my values.yaml file:
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
privileged: false
runAsGroup: 1000
runAsNonRoot: true
…See below my values.yaml file:
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
privileged: false
runAsGroup: 1000
runAsNonRoot: true
…See below my values.yaml file:
securityContext:
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
privileged: false
runAsGroup: 1000
runAsNonRoot: true
…Hi again,
I tested this also with chart version 3.0.0 and get some similar errors:
$ kubectl logs -n gitea-staging gitea-staging-postgresql-0
2021-08-15 12:29:20.846 UTC [62] LOG: …