https://bugs.exim.org/show_bug.cgi?id=2982
--- Comment #2 from ivanov17 <ivanov17@???> ---
Hello, Martin!
Maybe I didn't explain well what's going on.
I am running Exim in an OCI container. This assumes that only the Exim process
will run in the container.
Exim itself works well in a containerized environment. But there is a problem
with logging.
In containerized environments, logs are written to the container's standard
output. Thus, they can be read and collected from outside the container.
Exim doesn't allow logs to be sent to standard output. So I don't have the
ability to read and collect container logs in the normal way.
There is a workaround: we can create symlinks to /dev/stdout and /dev/stderr
instead of log files when creating a container image for Exim. It works, but
it's ugly.
Or we can run multiple processes in the same container. This is possible, but
requires process management via an entrypoint script. It is ugly and breaks
security standards.
Unfortunately, Exim cannot send log data to syslog daemon over tcp. If it were
possible, I could use another container running the syslog daemon. It would be
inconvenient, but better than running multiple processes in the same container.
In summary, the problem with Exim logging in containerized environments can
only be completely solved if Exim itself starts sending logs to standard
output.
--
You are receiving this mail because:
You are on the CC list for the bug.
