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.1 KiB
Django/Jinja
38 lines
1.1 KiB
Django/Jinja
#jinja2: lstrip_blocks: "True"
|
|
[Unit]
|
|
Description=Matrix Redis server
|
|
After=docker.service
|
|
Requires=docker.service
|
|
|
|
[Service]
|
|
Type=simple
|
|
ExecStartPre=-/usr/bin/docker stop matrix-redis
|
|
ExecStartPre=-/usr/bin/docker rm matrix-redis
|
|
|
|
ExecStart=/usr/bin/docker run --rm --name matrix-redis \
|
|
--log-driver=none \
|
|
--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
|
|
--cap-drop=ALL \
|
|
--read-only \
|
|
--tmpfs=/tmp:rw,noexec,nosuid,size=100m \
|
|
--network={{ matrix_docker_network }} \
|
|
{% if matrix_redis_container_redis_bind_port %}
|
|
-p {{ matrix_redis_container_redis_bind_port }}:6379 \
|
|
{% endif %}
|
|
--mount type=bind,src={{ matrix_redis_base_path }}/redis.conf,dst=/usr/local/etc/redis/redis.conf,ro \
|
|
--mount type=bind,src={{ matrix_redis_data_path }},dst=/data \
|
|
{% for arg in matrix_redis_container_extra_arguments %}
|
|
{{ arg }} \
|
|
{% endfor %}
|
|
{{ matrix_redis_docker_image_to_use }} \
|
|
redis-server /usr/local/etc/redis/redis.conf
|
|
|
|
ExecStopPost=-/usr/bin/docker stop matrix-redis
|
|
ExecStopPost=-/usr/bin/docker rm matrix-redis
|
|
Restart=always
|
|
RestartSec=30
|
|
SyslogIdentifier=matrix-redis
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|