e310d4e4f0
There is no need for osbuild-composer to wait until the whole multi-user target is completed. It can be started earlier as it doesn't have any dependencies in the target. This can be a problem if there is a unit in the target that is not starting and still is unrelated to osbuild-composer. There was a bug like this with Plymouth where the service didn't finish and it was hanging. That prevented osbuild-composer from starting and the user was left with working SSH connection and shell, but composer-cli and systemctl start osbuild-composer.service were both unresponsive. Replace After=multi-user.target with After=network.target to start osbuild-composer earlier. |
||
|---|---|---|
| .. | ||
| .env | ||
| docker-compose.yml | ||
| Dockerfile-ubi | ||
| Dockerfile-worker | ||
| osbuild-composer-api.socket | ||
| osbuild-composer-clouddot-template.yml | ||
| osbuild-composer.conf | ||
| osbuild-composer.service | ||
| osbuild-composer.socket | ||
| osbuild-local-worker.socket | ||
| osbuild-remote-worker.socket | ||
| osbuild-remote-worker@.service | ||
| osbuild-worker@.service | ||