https://bugs.exim.org/show_bug.cgi?id=2941
--- Comment #6 from ivanov17 <ivanov17@???> ---
Thank you, Jeremy and Heiko!
I am sorry for my lack of attention, I really missed the statement that options
that undergo string expansion before use are marked with †.
Now I'm using a simply configuration where I override the compiled settings and
default ports. I always have a stateless container that can run without
additional configuration, but I can set all other options in an included file
placed on a persistent volume. Also I can run Exim containers from
non-priveleged user and they works fine.
I can create an included configuration file from template using configuration
management tools like Ansible, and have different configurations in different
environments. Voila!
$ cat /etc/exim/exim.conf
# Override compiled settings
exim_user = 101
exim_group = 101
spool_directory = /data
log_file_path = /data/log/%slog : syslog
# Listen on unprivileged ports
daemon_smtp_ports = 2525 : 4465
tls_on_connect_ports = 4465
# Read configuration from a mounted volume
.include_if_exists /data/exim.conf
But there is a problem that I can't solve. Exim unable to write logs to
standard output. I can read container logs when I run the daemon with `-bdf`
option, but this only works with pseudo-TTY allocated to the container.
Unfortunately, I unable to collection logs from such containers.
I have searched the web for a solution, but everything that I found is ugly.
First, I can create symlinks to /dev/stdout and /dev/stderr instead of log
files. Another option is to run multiple processes in a container (xtail or a
syslog daemon). That is a wrong way, but even if I do, I need to write simple
process manager and in the case of the syslog daemon, I have to run it as root,
because it has to create /dev/log file.
So I think I should open a new issue for this.
--
You are receiving this mail because:
You are on the CC list for the bug.
