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.

Sign up for GitHub

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

Jump to bottom

Figure out better solution for bitnami postgresql images #156

Closed
edeandrea opened this issue Oct 6, 2022 · 0 comments · Fixed by #157
Closed

Figure out better solution for bitnami postgresql images #156

edeandrea opened this issue Oct 6, 2022 · 0 comments · Fixed by #157
Assignees
@edeandrea
Labels
enhancement New feature or request heroes-service Heroes service villains-service Villains service

Comments

@edeandrea
Copy link
Collaborator

The immediate fix for #154 was to revert back to a previous bitnami image. After some conversation on bitnami/containers#9143 we need to figure out a different way to pull in the Hero/Villain data which will allow us to not have to be pinned to this PostgreSQL image.

Some possible solutions:

  1. Maybe use an initContainer on the db pods for pulling the data to a shared volume?
  2. Switch away from the bitnami images to something else?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@edeandrea edeandrea

Labels
enhancement New feature or request heroes-service Heroes service villains-service Villains service
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use initcontainers for heroes/villains postgres initialization edeandrea/quarkus-super-heroes
1 participant
@edeandrea