316d653d3e
We run containers as a non-root user (no effective capabilities). Still, if a setuid binary is available in a container image, it could potentially be used to give the user the default capabilities that the container was started with. For Docker, the default set currently is: - "CAP_CHOWN" - "CAP_DAC_OVERRIDE" - "CAP_FSETID" - "CAP_FOWNER" - "CAP_MKNOD" - "CAP_NET_RAW" - "CAP_SETGID" - "CAP_SETUID" - "CAP_SETFCAP" - "CAP_SETPCAP" - "CAP_NET_BIND_SERVICE" - "CAP_SYS_CHROOT" - "CAP_KILL" - "CAP_AUDIT_WRITE" We'd rather prevent such a potential escalation by dropping ALL capabilities. The problem is nicely explained here: https://github.com/projectatomic/atomic-site/issues/203
32 lines
1 KiB
Django/Jinja
32 lines
1 KiB
Django/Jinja
[Unit]
|
|
Description=Matrix riot-web server
|
|
{% for service in matrix_riot_web_systemd_required_services_list %}
|
|
Requires={{ service }}
|
|
After={{ service }}
|
|
{% endfor %}
|
|
|
|
[Service]
|
|
Type=simple
|
|
ExecStartPre=-/usr/bin/docker kill matrix-riot-web
|
|
ExecStartPre=-/usr/bin/docker rm matrix-riot-web
|
|
ExecStart=/usr/bin/docker run --rm --name matrix-riot-web \
|
|
--log-driver=none \
|
|
--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
|
|
--cap-drop=ALL \
|
|
-v {{ matrix_riot_web_data_path }}/nginx.conf:/etc/nginx/nginx.conf:ro \
|
|
-v /dev/null:/etc/nginx/conf.d/default.conf:ro \
|
|
-v {{ matrix_riot_web_data_path }}/config.json:/etc/riot-web/config.json:ro \
|
|
-v {{ matrix_riot_web_data_path }}/home.html:/etc/riot-web/home.html:ro \
|
|
--network={{ matrix_docker_network }} \
|
|
{% if matrix_riot_web_container_expose_port %}
|
|
-p 127.0.0.1:8765:8080 \
|
|
{% endif %}
|
|
{{ matrix_riot_web_docker_image }}
|
|
ExecStop=-/usr/bin/docker kill matrix-riot-web
|
|
ExecStop=-/usr/bin/docker rm matrix-riot-web
|
|
Restart=always
|
|
RestartSec=30
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|