-
Notifications
You must be signed in to change notification settings - Fork 620
Teedy version does not exist and environment variables set up wrong #1422
Comments
We've bumped the image version to v1.10. We've not yet looked at the env vars though. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions. |
This is still valid afaik |
@bjw-s How do I get the bot to remove the stale tag? |
I just checked, and we don't set any value for the env var, not even an empty string: the output of env:
- name: "DATABASE_PASSWORD"
value:
- name: "DATABASE_URL"
value: That should mean the env var will be present in the container but should not have a value. Since it seems the application does not handle that well, the way forward would be to comment out the default env vars completely and leave it up to the user to specify the ones they desire. Feel free to open up a PR if we don't get around to fixing it in the meantime. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions. |
Details
Helm chart name and version:
Teedy 5.5.0
Container name and tag:
v1.10
What steps did you take and what happened:
First, the chart references version teedy v1.9 (the tag no longer exists in dockerhub for some reason).
Second, when starting the chart without Postgres enabled, the container enters a CrashLoopBackOff state.
This is because the application checks whether the environment variable is null. Your helm chart is setting it to the empty string.
Relevant Helm values:
What did you expect to happen:
The image to start.
Anything else you would like to add:
Additional Information:
The text was updated successfully, but these errors were encountered: