mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2024-12-27 03:18:31 +01:00
86c36523df
Revertsb1b4ba501f,90c9801c56,a3c84f78ca, .. I haven't really traced it (yet), but on some servers, I'm observing `ansible-playbook ... --tags=start` completing very slowly, waiting to stop services. I can't reproduce this on all Matrix servers I manage. I suspect that either the systemd version is to blame or that some specific service is not responding well to some `docker kill/rm` command. `ExecStop` seems to work great in all cases and it's what we've been using for a very long time, so I'm reverting to that.
32 lines
1.1 KiB
Django/Jinja
32 lines
1.1 KiB
Django/Jinja
#jinja2: lstrip_blocks: "True"
|
|
[Unit]
|
|
Description=Automatic Backup of Matrix Postgres server
|
|
After=docker.service
|
|
Requires=docker.service
|
|
DefaultDependencies=no
|
|
|
|
[Service]
|
|
Type=simple
|
|
Environment="HOME={{ matrix_systemd_unit_home_path }}"
|
|
ExecStartPre=-{{ matrix_host_command_docker }} stop matrix-postgres-backup
|
|
ExecStartPre=-{{ matrix_host_command_sh }} -c '{{ matrix_host_command_docker }} rm matrix-postgres-backup 2>/dev/null'
|
|
|
|
ExecStart={{ matrix_host_command_docker }} run --rm --name matrix-postgres-backup \
|
|
--log-driver=none \
|
|
--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
|
|
--cap-drop=ALL \
|
|
--read-only \
|
|
--network={{ matrix_docker_network }} \
|
|
--env-file={{ matrix_postgres_backup_path }}/env-postgres-backup \
|
|
--mount type=bind,src={{ matrix_postgres_backup_path }},dst=/backups \
|
|
{{ matrix_postgres_backup_docker_image_to_use }}
|
|
|
|
ExecStop=-{{ matrix_host_command_docker }} stop matrix-postgres-backup
|
|
ExecStop=-{{ matrix_host_command_sh }} -c '{{ matrix_host_command_docker }} rm matrix-postgres-backup 2>/dev/null'
|
|
Restart=always
|
|
RestartSec=30
|
|
SyslogIdentifier=matrix-postgres-backup
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|