Hello, I have followed <https://www.ory.sh/docs/h...
# talk-hydra
p
Hello, I have followed https://www.ory.sh/docs/hydra/guides/kubernetes-helm-chart documentation for Kubernetes installation. The Helm installation goes fine but I can see one pod is failing.
Copy code
k get pods
NAME                      READY  STATUS       RESTARTS  AGE
hydra-example-67fb868bb6-45zdl         0/1   CrashLoopBackOff  35     156m
hydra-example-hydra-maester-84b64bdc79-46rm4  1/1   Running      0     156m
hydra-example-idp-678698b668-xjv4t       1/1   Running      0     160m
Below is the details which I can see in the pod description.
Copy code
State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 06 Apr 2022 16:41:39 +0530
      Finished:     Wed, 06 Apr 2022 16:41:39 +0530
    Ready:          False
    Restart Count:  36
    Liveness:       http-get http://:http-admin/health/alive delay=30s timeout=1s period=10s #success=1 #failure=5
    Readiness:      http-get http://:http-admin/health/ready delay=30s timeout=1s period=10s #success=1 #failure=5
    Environment:
      URLS_SELF_ISSUER:  <http://public.hydra.localhost/>
      DSN:               <set to the key 'dsn' in secret 'hydra-example'>            Optional: false
      SECRETS_SYSTEM:    <set to the key 'secretsSystem' in secret 'hydra-example'>  Optional: false
      SECRETS_COOKIE:    <set to the key 'secretsCookie' in secret 'hydra-example'>  Optional: false
    Mounts:
      /etc/config from hydra-config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from hydra-example-token-scwpr (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  hydra-config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      hydra-example
    Optional:  false
  hydra-example-token-scwpr:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  hydra-example-token-scwpr
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     <http://node.kubernetes.io/not-ready:NoExecute|node.kubernetes.io/not-ready:NoExecute> op=Exists for 300s
                 <http://node.kubernetes.io/unreachable:NoExecute|node.kubernetes.io/unreachable:NoExecute> op=Exists for 300s
Events:
  Type     Reason   Age                     From     Message
  ----     ------   ----                    ----     -------
  Warning  BackOff  4m25s (x736 over 159m)  kubelet  Back-off restarting failed container
t
Do the pod logs give any insight into why it's in the
CrashLoopBackOff
state?
p
Copy code
time=2022-04-06T14:31:19Z level=fatal msg=Unable to create service registry. audience=application error=map[message:the DSN connection string looks like a SQLite connection, but SQLite support was not built into the binary. Please check if you have downloaded the correct binary or are using the correct Docker Image. Binary archives and Docker Images indicate SQLite support by appending the -sqlite suffix] service_name=ORY Hydra service_version=v1.10.5
t
That'll be the problem. You're passing a SQLite DSN, but not using a docker image compatible with SQLite. The latest image to use with SQLite is
oryd/hydra:v1.10.7-sqlite