Dave Dewey writes:
As someone who has just done this myself, and in similar circumstances (longtime mm2 admin moving to mm3), I agree the documentation could use some assistance. I struggled with a couple of really basic issues setting up the docker implementation -
*sigh* We don't support that officially, either. That's a personal project of Abhilash's. As far as I know, he still considers it a proof of concept, not a product for general use.
We really only are in a position to provide good support for installations via pip, from the most recent release or from git HEADs. The virtualenv install is preferred, but as long as you provide the installation paths from mailman.cfg, we'll be able to give good support. Everything else is "we'll try, maybe you'll get lucky".
something as fundamental as understanding what the file structure on the disk should be outside of the docker containers. I got through it and took some decent notes with a goal of simplifying and automating this for myself… maybe a couple of us could contribute to fill in gaps we found.
That would be a big step toward official support. You're welcome to discuss the docker installation (and distro packages, for that matter) here, but issues and MRs should be filed to the docker-mailman project on GitHub, not the Mailman project on GitLab (or the distro package, in that case).
It would also be very helpful to provide advice on Docker networking (basic theory of operation, list of IPs that need to be coordinated across containers come to mind). I hadn't heard of the host filesystem issue before (but I easily imagine that could be a source of confusion), while "Docker networking hates me" is a FAQ.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan