Description
I've noticed that after an arkdep build/deploy/reboot that there are some Systemd Services that are not enabled and thus not started.
For example cronie and sshd
However NetworkManager and sddm (I'm using KDE) are enabled and started.
Does your build process mark NetworkManager and sddm as enabled in some way?
As I'm not an Arch guru, is there an Arch or Systemd configuration for this [for initial boot]?
I'm not asking about systemctl enable cronie
I'm saying that executing the this and others manually after every image build and reboot seems ridiculous
If there's no available solution for this, then I guess I'm asking for a rc.local type of solution!!!
Perhaps you could add examples for cronie and sshd to your documentation , together with /arkdep/config, migrate_files=('/etc/ssh') to avoid new keys being generated on each new image reboot.
(Also, annoyingly sudo always issues the first time warning)
Do you get this? I've done the arkdep build/deploy/reboot cycle many many times now and notice that are download and unpacking errors now and again.
Thanks
John