blue-build / modules

BlueBuild standard modules used for building your Atomic Images
Apache License 2.0
21 stars 27 forks source link

fix(systemd) service not starting automatically #227

Closed mecattaf closed 1 month ago

mecattaf commented 1 month ago

I have the following in my recipe.yml:

  - type: systemd
  - system:
    enabled:
     - sddm-boot.service
     - tailscaled.service
     - input-groupadd.service
    disabled:
     - rpm-ostree-countme.timer

I have verified that tailscaled.service exists with systemctl status tailscaled.service

Despite it being listed under "enabled" in the module, the service gets listed as "inactive (dead)" by default. I am able to manually solve this by doing:

sudo systemctl enable tailscaled.service
sudo systemctl start tailscaled.service

Is this expected behavior? Am I doing something wrong?

Many thanks

fiftydinar commented 1 month ago

As @gmpinder noted in Discord server, the issue is because of the wrong yml syntax.

It should be like this:

  - type: systemd
    system:
      enabled:
        - sddm-boot.service
        - input-groupadd.service
        - tailscaled.service
      disabled:
        - rpm-ostree-countme.timer

We are aiming to avoid this scenario in the future by implementing yaml syntax validation.

I will close this issue as solved, if you still have problem related to this, please reopen.

mecattaf commented 1 month ago

Thanks for the feedback!