> nor do the authors care about "this silly new fad"
In fairness, if you have chosen a platform that potentially introduces its own issues that isn't their problem unless they want it to be.
A friend of mine has a project out there that only has official builds and build instructions for plain debian-based Linux, and he finds demands for direct docker support to be irritating (far worse than demands for a supported native Windows build ever were). And demand is the right word: many don't just ask, and some seem to get personally offended when he responds that he doesn't use docker much himself so wouldn't be comfortable offering support for it directly.
Sure, it's the author's right to choose what to support and what not. But I'd argue that software openly hostile to docker is probably not the best choice as central piece of your docker-compose based emailling setup, if the alternative is a single golang binary designed for use with docker.
> But I'd argue that software openly hostile to docker is probably not the best choice as central piece of your docker-compose based emailling setup
What are you referring to? Because Mailu isn't Docker-hostile, quite the opposite: it is distributed as a set of Docker containers. And dspillett didn't mention what was his friend's project about, it could be totally unrelated to email.
In fairness, if you have chosen a platform that potentially introduces its own issues that isn't their problem unless they want it to be.
A friend of mine has a project out there that only has official builds and build instructions for plain debian-based Linux, and he finds demands for direct docker support to be irritating (far worse than demands for a supported native Windows build ever were). And demand is the right word: many don't just ask, and some seem to get personally offended when he responds that he doesn't use docker much himself so wouldn't be comfortable offering support for it directly.