Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default database in helm chart is mysql resulting in CrashLoopBackoff - sqlite3 is needed to start container successfully #808

Open
ehlowr0ld opened this issue Nov 5, 2024 · 0 comments

Comments

@ehlowr0ld
Copy link

Describe the bug (must be provided)

The container is hanging in CrashLoopBackoff if you simply deplyo the chard.
Configmap must be changed to user database_type sqlite3 to start cleanly in ubernetes env.
Alternatively a mysql mus be deployed and the address adjusted in configmap - which is not very hands-free way like you would expect from helm chart.

A parameter in values.yml would be useful.

Your Environments (must be provided)

  • OS: Linux / Kubernetes / Helm
  • Node-version: shipped version in container image
  • Studio-version: 3.10.0, master

How To Reproduce(must be provided)

Steps to reproduce the behavior:

  1. Deploy the chart

Expected behavior

Container starts

Additional context

Provide logs and configs, or any other context to trace the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant