It might be worth taking a step back and looking at your objective with all of this and why you are doing it in the first place.
If it’s for privacy, then unfortunately that ship has sailed when it comes to email. It’s the digital equivalent of a post card. It’s inherently not private. Nothing you do will make it private. Even services like proton Mail aren’t private–unless you only email other people on proton.
I appreciate wanting to control your own destiny with it but there are much more productive things you could be spending your time on the improve your privacy surface area.
Breaking things is the best way to learn. Accidentally deleting your container data is one of the best ways to learn how to not do that AND learn about proper backups.
Breaking things and then trying to restore from a backup that…doesn’t work. Is a great way to learn about testing backups and/or properly configuring them.
The corrolary to this is: just do stuff. Analysis paralysis is real. You can look up a dozen “right ways” to do things and end up never starting.
My advice: just start. If you end up backing yourself into a corner where you can’t scale or easily migrate to another solution, oh well. You either learn that lesson or figure out a way to migrate. Learning all along the way.
Each failure or screw up is worth a hundred “best practice / how to articles”.
Isn’t this just a basic legal concept?
“In order to claim damages, there must be a breach in the duty of the defendant towards the plaintiff, which results in an injury”
Basically the judge is saying the plaintiff didn’t establish the basic foundation of a tort case. He’s not saying this isn’t wrong, he’s saying they didn’t present the case in a way that proves it.
It’s not enough to say “you shouldn’t be doing this”–even if that’s true.
The major think noobs tend to mess up with docker is not setting up volumes properly so when you get rid of the instance, you lose all of your data.
I also highly recommend docker-compose for ease of use.
Id recommend looking up security best practices for docker as well. Things like setting a user id & gid for the containers add an additional layer of security.
Oh and make sure you get your containers from trustworthy sources.
I think you are obligated to share your entire known hosts file to prove this.