b1b4ba501f
ExecStopPost should allow us to clean up (docker kill + docker rm) even if the ExecStart (docker run ..) command failed, and not just after a graceful service stop was initiated. Source: https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStopPost=
38 lines
1.4 KiB
Django/Jinja
38 lines
1.4 KiB
Django/Jinja
#jinja2: lstrip_blocks: "True"
|
|
[Unit]
|
|
Description=Matrix mailer
|
|
After=docker.service
|
|
Requires=docker.service
|
|
DefaultDependencies=no
|
|
|
|
[Service]
|
|
Type=simple
|
|
Environment="HOME={{ matrix_systemd_unit_home_path }}"
|
|
ExecStartPre=-{{ matrix_host_command_sh }} -c '{{ matrix_host_command_docker }} kill matrix-mailer 2>/dev/null'
|
|
ExecStartPre=-{{ matrix_host_command_sh }} -c '{{ matrix_host_command_docker }} rm matrix-mailer 2>/dev/null'
|
|
|
|
# --hostname gives us a friendlier hostname than the default.
|
|
# The real hostname is passed via a `HOSTNAME` environment variable though.
|
|
ExecStart={{ matrix_host_command_docker }} run --rm --name matrix-mailer \
|
|
--log-driver=none \
|
|
--user={{ matrix_mailer_container_user_uid }}:{{ matrix_mailer_container_user_gid }} \
|
|
--cap-drop=ALL \
|
|
--read-only \
|
|
--tmpfs=/var/spool/exim:rw,noexec,nosuid,size=100m \
|
|
--network={{ matrix_docker_network }} \
|
|
--env-file={{ matrix_mailer_base_path }}/env-mailer \
|
|
--hostname=matrix-mailer \
|
|
{% for arg in matrix_mailer_container_extra_arguments %}
|
|
{{ arg }} \
|
|
{% endfor %}
|
|
{{ matrix_mailer_docker_image }}
|
|
|
|
ExecStopPost=-{{ matrix_host_command_sh }} -c '{{ matrix_host_command_docker }} kill matrix-mailer 2>/dev/null'
|
|
ExecStopPost=-{{ matrix_host_command_sh }} -c '{{ matrix_host_command_docker }} rm matrix-mailer 2>/dev/null'
|
|
Restart=always
|
|
RestartSec=30
|
|
SyslogIdentifier=matrix-mailer
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|