Move Django database and keytabs to podman volume #108
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In order to persist information between container executions, we should mount data such as keytabs as a volume. This change centralizes keytabs and Django database so that everything can be mounted to a single volume if specified by the user. Signed-off-by: Antonio Torres <antorres@redhat.com>
antoniotorresm
force-pushed
the
podmanvolume2
branch
from
a4c37b0 to
9a7e853
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to persist information between container executions, we should mount data such as keytabs as a volume. This change centralizes keytabs and Django database so that everything can be mounted to a single volume if specified by the user.