Exim Container integration (support files for systemd and (podman|docker) compose)
Find a file
2026-02-02 14:51:33 +01:00
debian Update changelog for 0.1.2 release 2026-01-10 21:55:39 +01:00
.gitignore new: Makefile, local build 2026-02-02 14:08:09 +01:00
compose.yaml new:doc: add example for build instructions 2026-01-10 21:54:28 +01:00
exim-container.spec new: Makefile, local build 2026-02-02 14:08:09 +01:00
exim-container@.service new: debian package for exim-container 2026-01-04 16:34:29 +01:00
eximsh fix: usermerge 2026-02-02 14:51:33 +01:00
Makefile new: Makefile, local build 2026-02-02 14:08:09 +01:00
README.md new:doc: add hint on running dns service 2026-01-10 21:54:59 +01:00

System integration

The systemd unit file is provided for Exim container installation. It requires /etc/exim/container/<instance.yaml>

Unsorted notes

Podman configuration

If you run Podman, "podman compose" will use the configured compose provider. It defaults to "docker compose", but can be switched in containers.conf.

E.g. for system wide configuration, add to /etc/containers/containers.conf:

[engine]
compose_providers = ["podman-compose"]
compose_warning_logs = false            # switch off warnings about the compose provider

DNS

If there is a DNS server running, podman might fail to startup its own DNS listener (symtom: port in use). Restrict the DNS server (e.g. Bind) to the required interfaces (addresses).

Commands

Command command "prefix":

podman compose --podman-run-args=--replace -p <project> -f <compose-file>
  • startup

    podman … up
    
  • reload

    podman … kill --signal HUP daemon
    

    Where exim is the name of the service (defined in the compose file)

  • execute any command in the running container

    podman … exec daemon <command>
    
  • run any command in a new ephemral container

    podman … run --rm daemon <command>
    

There is a command "proxy" for the most important commands