Re: PATCH: Keep Postfix running in the foreground

2017-12-19 Thread Wietse Venema
Eray Aslan: > On Tue, Dec 19, 2017 at 10:53:38AM -0500, Wietse Venema wrote: > > Postfix will bail out if it knows that the queue or data directory > > are shared, because that can result in data corruption. > > > > How do I enforce that constraint when directories are imported into > > a containe

Re: PATCH: Keep Postfix running in the foreground

2017-12-19 Thread Eray Aslan
On Tue, Dec 19, 2017 at 10:53:38AM -0500, Wietse Venema wrote: > Postfix will bail out if it knows that the queue or data directory > are shared, because that can result in data corruption. > > How do I enforce that constraint when directories are imported into > a container from the host? I don'

Re: PATCH: Keep Postfix running in the foreground

2017-12-19 Thread Wietse Venema
Viktor Dukhovni: > > > > On Dec 19, 2017, at 10:19 AM, Eray Aslan wrote: > > > > Usually sending log output to console is the preferred approach. If we > > cannot do it natively, having syslog daemon write to console (in > > addition to local log file?) looks like a better option than importin

Re: PATCH: Keep Postfix running in the foreground

2017-12-19 Thread Viktor Dukhovni
> On Dec 19, 2017, at 10:19 AM, Eray Aslan wrote: > > Usually sending log output to console is the preferred approach. If we > cannot do it natively, having syslog daemon write to console (in > addition to local log file?) looks like a better option than importing > sockets from the host. Not

Re: PATCH: Keep Postfix running in the foreground

2017-12-19 Thread Wietse Venema
Eray Aslan: > On Tue, Dec 19, 2017 at 10:01:53AM -0500, Wietse Venema wrote: > > I suppose one approach is to make a Postfix container disposable, > > i.e. a container is never updated with a new Postfix version, but > > it is replaced with a newer one > > That is the common Docker approach. Imag

Re: PATCH: Keep Postfix running in the foreground

2017-12-19 Thread Eray Aslan
On Tue, Dec 19, 2017 at 10:01:53AM -0500, Wietse Venema wrote: > I suppose one approach is to make a Postfix container disposable, > i.e. a container is never updated with a new Postfix version, but > it is replaced with a newer one That is the common Docker approach. Images are immutable. > and

PATCH: Keep Postfix running in the foreground

2017-12-19 Thread Wietse Venema
Wietse Venema: > I think that Docker fundamentally wants one service instance per > container. On Postfix service instance translates into one queue, > for example submission+smtp sharing one queue, similar to http+https > sharing one website. Let's not fight the Docker approach, and leave > orches