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
This commit is contained in:
parent
d23d57bc31
commit
ed185b41ce
11 changed files with 88 additions and 34 deletions
2
go.sum
2
go.sum
|
|
@ -1,3 +1,5 @@
|
|||
github.com/coreos/go-systemd v0.0.0-20190719114852-fd7a80b32e1f h1:JOrtw2xFKzlg+cbHpyrpLDmnN1HqhBfnX7WDiW7eG2c=
|
||||
github.com/coreos/go-systemd v0.0.0-20190719114852-fd7a80b32e1f/go.mod h1:F5haX7vjVVG0kc13fIWeqUViNPyEJxv/OmvnBo0Yme4=
|
||||
github.com/google/uuid v1.1.1 h1:Gkbcsh/GbpXz7lPftLA3P6TYMwjCLYm83jiFQZF/3gY=
|
||||
github.com/google/uuid v1.1.1/go.mod h1:TIyPZe4MgqvfeYDBFedMoGGpEw/LqOeaOT+nhxU+yHo=
|
||||
github.com/julienschmidt/httprouter v1.2.0 h1:TDTW5Yz1mjftljbcKqRcrYhd4XeOoI98t+9HbQbYf7g=
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue