![]() ![]() Postgresql 06:27:15.77 Submit issues and feature requests at Postgresql 06:27:15.77 Subscribe to project updates by watching Postgresql 06:27:15.77 Welcome to the Bitnami postgresql container While going through this output, I found that there is some problem with the database and I checked the output of database pod logs microk8s kubectl logs gitea-postgresql-0 Gitea migrate might fail due to database connection.This init-container will try again in a few seconds Warning BackOff 34s (圆833 over 25h) kubelet Back-off restarting failed containerĪlso checked the output of configure-gitea microk8s kubectl logs gitea-0 -c configure-giteaġ 07:37:39 cmd/migrate.go:34:runMigrate() AppPath: /usr/local/bin/giteaġ 07:37:39 cmd/migrate.go:35:runMigrate() AppWorkPath: /dataġ 07:37:39 cmd/migrate.go:36:runMigrate() Custom path: /data/giteaġ 07:37:39 cmd/migrate.go:37:runMigrate() Log path: /data/logġ 07:37:39 cmd/migrate.go:38:runMigrate() Configuration file: /data/gitea/conf/app.iniġ 07:37:44 cmd/migrate.go:41:runMigrate() Failed to initialize ORM engine: dial tcp: lookup .local: Try again unreachable:NoExecute op=Exists for 300s Tolerations: /not-ready:NoExecute op=Exists for 300s Type: Projected (a volume that contains injected data from multiple sources) ![]() Type: EmptyDir (a temporary directory that shares a pod's lifetime) Type: Secret (a volume populated by a Secret) Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) Readiness: tcp-socket :http delay=5s timeout=1s period=10s #success=1 #failure=3 Liveness: tcp-socket :http delay=200s timeout=1s period=10s #success=1 #failure=10 ![]() So I checked the output of the gitea pod describe command ant the output is microk8s kubectl describe pod gitea-0Ĭontroller-revision-hash=gitea-7b7874bd4c The pods are running fine except the gitea pod default gitea-memcached-79c5884c97-62khj 1/1 Running 0 25hĭefault gitea-postgresql-0 1/1 Running 0 25hĭefault gitea-0 0/1 Init:CrashLoopBackOff 294 (4m1s ago) 25h Now I ran the helm install command -> helm install -dependency-update gitea. I am trying to deploy gitea with the help of the helm chart and I am using the microk8s in CentOS environment, but I am unable to deploy gitea.įirst I cloned the gitea helm chart using the command : git clone Īfter that I changed storage class value in the values.yaml to set the default storage to the microk8s-hostpath persistence: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |