Add postfix-runtime volume for queue_directory/data_directory - #57
Open
chrisblech wants to merge 1 commit into
Open
Add postfix-runtime volume for queue_directory/data_directory#57chrisblech wants to merge 1 commit into
chrisblech wants to merge 1 commit into
Conversation
Postfix's queue_directory (/var/spool/postfix) and data_directory (/var/lib/postfix) previously had no persistent storage, so the mail queue and TLS session caches were lost on every container recreate. Point both at a single postfix-runtime named volume instead, and have the entrypoint create the directory tree and fix ownership on every start via "postfix check" + "postfix set-permissions" (idempotent, so it's safe on both first run and subsequent restarts).
This file contains hidden or 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
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.
Postfix's queue_directory (/var/spool/postfix) and data_directory (/var/lib/postfix) previously had no persistent storage, so the mail queue and TLS session caches were lost on every container recreate. Point both at a single postfix-runtime named volume instead, and have the entrypoint create the directory tree and fix ownership on every start via "postfix check" + "postfix set-permissions" (idempotent, so it's safe on both first run and subsequent restarts).
Should be merged before integrating #55 , so states of all clients (i.e. temp-whitelists) for postscreen survive container restarts, rebuilds, crashes.