Define a volume for the caching Redis #852
Merged
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.
Related Issue: #851
New Behavior
Prevent the creation of a temporary volume for the caching redis
Contrast to Current Behavior
Docker automatically creates a volume for
/data
, as the Container manifest of redis defines a volume.Discussion: Benefits and Drawbacks
The benefit is that less unmanaged volumes are created and that the ones who are created, that these are controllable. (E.g. that they respond to
docker compose down -v
, which removes all managed volumes.)Changes to the Wiki
n/a
Proposed Release Note Entry
Pre-defined volume for the caching redis, to prevent the container runtime from creating an temporary unmanaged volume.
Double Check
develop
branch.