24cf27c60c
Most (all?) of our Matrix services are running in the `matrix` network, so they were safe -- not accessible from Coturn to begin with. Isolating Coturn into its own network is a security improvement for people who were starting other services in the default Docker network. Those services were potentially reachable over the private Docker network from Coturn. Discussed in #120 (Github Pull Request)
32 lines
1.0 KiB
Django/Jinja
32 lines
1.0 KiB
Django/Jinja
[Unit]
|
|
Description=Matrix Coturn server
|
|
{% for service in matrix_coturn_systemd_required_services_list %}
|
|
Requires={{ service }}
|
|
After={{ service }}
|
|
{% endfor %}
|
|
|
|
[Service]
|
|
Type=simple
|
|
ExecStartPre=-/usr/bin/docker kill matrix-coturn
|
|
ExecStartPre=-/usr/bin/docker rm matrix-coturn
|
|
ExecStart=/usr/bin/docker run --rm --name matrix-coturn \
|
|
--log-driver=none \
|
|
--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
|
|
--cap-drop=ALL \
|
|
--read-only \
|
|
--tmpfs=/var/tmp:rw,noexec,nosuid,size=100m \
|
|
--network={{ matrix_coturn_docker_network }} \
|
|
-p 3478:3478 \
|
|
-p 3478:3478/udp \
|
|
-p {{ matrix_coturn_turn_udp_min_port }}-{{ matrix_coturn_turn_udp_max_port }}:{{ matrix_coturn_turn_udp_min_port }}-{{ matrix_coturn_turn_udp_max_port }}/udp \
|
|
-v {{ matrix_coturn_config_path }}:/turnserver.conf:ro \
|
|
{{ matrix_coturn_docker_image }} \
|
|
-c /turnserver.conf
|
|
ExecStop=-/usr/bin/docker kill matrix-coturn
|
|
ExecStop=-/usr/bin/docker rm matrix-coturn
|
|
Restart=always
|
|
RestartSec=30
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|