Use bind mounts in sample config#2035
Conversation
|
Actually a good idea. But this requires a documentation update. |
|
For sure. But before wasting time, I wanted to know beforehand what your opinions are 😎 |
|
I prefer bind mounts over volumes (personal opinion) so you have my vote |
polarathene
left a comment
There was a problem hiding this comment.
Might be worth adding to the FAQ how to restore?
I also wanted to be a bit more explicit about the option for compressing to gzip. I'd suggest --zstd with tar.zst but not sure how wide the support for that is.
Doesn't that mess with permissions / ownership metadata on files? I prefer bind mounts myself, but a common issue I can run into with containers is the container writes the files with different uid/gid (mostly only an annoyance if you're non-root), or you configure some files from the host side and if the container lacks permission to read/write the file it gets upset. Regarding the referenced issue, kinda seems odd to backup clamav bloat, depending on the age of the backup when it's restored, I'm not sure how worthwhile that would be to retain? This is still a nice improvement anyway :) |
I think creating a |
Yeah, that's why I was reluctant with my preference to use zstd (which is definitely better when available). I'd still prefer the more explicit option of |
I prefer verbosity, too. Always hard for future contributions to look up / follow along if a bunch of short options is thrown together using a tool a contributor might not know. As most will copy/paste it anyways it should not be a big deal |
|
Yes. We will use the long option |
|
@docker-mailserver/maintainers feel free to edit/add docu yourself to this PR 👍 This was just a first attempt. I was too tired to continue yesterday. |
Co-authored-by: Brennan Kinney <[email protected]>
Not all tar versions do support auto detection of compression.
|
Documentation preview for this PR is ready! 🎉 Built with commit: a2d3dea |
|
❤️ |
Description
If we switch to bind mounts in the sample config, that will simplify backup/restore of DMS.
See also: #1906
This would also make the not 100% correct working script at https://docker-mailserver.github.io/docker-mailserver/edge/faq/#what-about-backups obsolete.
Backup/restore would then just be simple host commands
cp / mv..What do you think?
Type of change
Checklist:
docs/)