Hydra -sqlite image should be used when dsn is set to memory

[mrtndwrd]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Cloud project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

When I run helm install with hydra.config.dsn set to memory, I expect this to work. But the container crashloops with the following message in the log:

time=2021-11-12T11:11:49Z 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

It appears that the in-memory database is based on SQLite, but that is not included in this chart's default image. I think the solution would be to optionally add -sqlite to the image tag in this chart.

Reproducing the bug

1. helm repo add ory https://k8s.ory.sh/helm/charts
2. helm repo update
3. As suggested in the docs:

   helm install \
    --set 'hydra.config.secrets.system={'$(LC_ALL=C tr -dc 'A-Za-z0-9' < /dev/urandom | base64 | head -c 32)'}' \
    --set 'hydra.config.dsn=memory' \
    --set 'hydra.config.urls.self.issuer=https://my-hydra/' \
    --set 'hydra.config.urls.login=https://my-idp/login' \
    --set 'hydra.config.urls.consent=https://my-idp/consent' \
    hydra-test \
    ory/hydra
   

Relevant log output

kubectl logs hydra-test-6548bc5bc8-4rwc9
time=2021-11-12T13:09:46Z 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

### Relevant configuration

```yml
hydra:
  config:
    dsn: memory

Version

Hydra Chart 0.20.2

On which operating system are you observing this issue?

Linux

In which environment are you deploying?

Kubernetes with Helm

Additional Context

No response

[aeneasr]

dsn: memory is really only for local testing. It won't work well in Kubernetes, so we don't want to encourage it. Just scaling hydra to two nodes with dsn: memory and you will end up with two databases! So I think this a nofix because it encourages behavior which is not suitable for a Kubernetes environment :/

[mrtndwrd]

Thanks for the quick reply!

I see your reasoning. We're currently running super small Kubernetes environments. At what point (how many users?) is an admin expected to scale up to two Hydra pods? I have the feeling that this would be pretty helpful for my use case...

If it's a nofix: at least the documentation should be updated. The issue description includes a copy-paste of the installation instructions which I would expect to work.

[aeneasr]

That makes sense, would be awesome if you could contribute that to the docs :)

Production should always use at least two pods to ensure rolling restarts and other kubernetes/cloud-native deployment methodologies are working.