We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I hope to find a suitable image here.
The text was updated successfully, but these errors were encountered:
I wonder what use case would justify that combination, because it'd tightly couple the backend and the persistence layer.
In other words, any change to the backend would directly impact the database instance that already has production data.
Even in the pre-containerization era, the database was running elsewhere for this very reason.
Either way, you can always create your own custom Dockerfile to cater to this combination, since no such image appears to exist on DockerHub.
Sorry, something went wrong.
No branches or pull requests
I hope to find a suitable image here.
The text was updated successfully, but these errors were encountered: