debian-forge-composer/distribution/osbuild-worker.service
Martin Sehnoutka ed185b41ce Integration of osbuild composer with systemd
osbuild-composer now uses socket activation instead of hardcoded paths
in the code. osbuild-worker is an http client therefore it uses only
service unit. osbuild-worker must be started after the socket is
created. osbuild-composer service requires osbuild-worker to run, because without
it no jobs can be started.

osbuild-composer is executed as a regular user (newly created
_osbuild-composer user) as opposed to the worker which must run as root
in order to execute osbuild itself
2019-10-02 17:56:59 +02:00

15 lines
328 B
Desktop File

[Unit]
Description=OSBuild Composer Worker (%i)
After=multi-user.target osbuild-composer.socket
[Service]
Type=simple
PrivateTmp=true
ExecStart=/usr/lib/osbuild-composer/osbuild-worker -C /var/lib/osbuild
CacheDirectory=osbuild-composer
Restart=on-failure
RestartSec=10s
[Install]
DefaultInstance=1
WantedBy=multi-user.target