Nico Schottelius:
>
> Salut Wietse,
>
> Wietse Venema via Postfix-users <postfix-users@postfix.org> writes:>
> > [...]
> > If there are 'common' container use cases, then I suppose that
> > Postfix could distrtibute example Dockerfiles for that.
>
> While the use cases are likely to differ, a lot of "common" software
> such as nginx provide minimal containers that simply start the software,
> w/o any specific configuration.
Right. Postfix is fundamentally different from a web server that
passively waits for connections. Postix also needs to know how to
deliver mail.
If Postfix is used as an internal server that forwards mail from a
local process or container to a smarthost, then that needs to be
configured. Postfix supports service discovery with SRV records in
DNS, that may help.
If Postfix is used as an Internet-exposed mail server, then it needs
to know its public hostname and IP address, and a couple other
things that are needed to receive and deliver mail through today's
Internet.
And these are just two common examples.
> My suggestion - or wish - for postfix would be if it could follow
> footsteps of nginx in the sense that there are 1-2 containers (not only
> Dockerfiles) published per version, such as:
>
> versionx-alpine
> versiony-debian
>
> The Dockerfiles for both of them could be as simple as apk add / apt-get
> install plus the entrypint "postfix start-fg". As to which configuration
> would be placed inside the container, that is up to the user.
>
> The required work for this would be:
>
> - a) Create 1-2 Dockerfiles
> - b) Create a new container once a new version is released & added into the
> specific distribution
>
> I could help (a) and/or (b), but it would need someone (I guess you) to
> define which/where the "official" container image would be located at
I can offer an official location for Dockerfile examples: in the
Postfix documentation, ready to copy-and-paste, with examples for
adjusting the configuration to the local use case.
Usage:
1) Cut and paste a Dockerfile example from Postfix website.
2) Add some "RUN postconf" commands to customize to local use case.
3) Run "docker build", and push to local or remote repo.
Here is another question that never got a good answer: containers
are supposed to be build-deploy-discard, i.e. they are not supposed
to be patched. How do people deal with with messages that are still
queued when a container needs to be decommissioned?
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
