dfunckt
dfunckt
Thanks for your PR. What is your use-case? systemd is baked into the [base image](https://github.com/balena-io-modules/open-balena-base) but we're also maintaining a "no-systemd" line which you'll need to switch to.
Absolutely, I agree, systemd in balena services is legacy really and there's no longer a reason to use it. I'm just curious what prompted you to get it removed.
I see, thanks. I've got to warn you this isn't going to be straightforward, but I'm happy to help as I can.
Tests need to pass. Check [CircleCI](https://circleci.com/gh/balena-io/open-balena-api/13627) to see details about what's wrong.
You need to separate the Change-type footer with one blank line from the commit description. The idea behind Change-type is to automatically bump the project version but also update CHANGELOG.md...
This change breaks support for mDNS (because the non-systemd base image lacks Avahi) so I'll need a few days before I merge as I'd like to see how we're solving...
The API isn't using or cares about mDNS but openBalena (and some other internal use cases) does when deploying an instance under a `.local` TLD.
@robbe-haesendonck I had a chat with the team and we're in agreement that in principle removing systemd from our services is desirable. We have a few ideas how to fill...
This is related: https://github.com/balena-io/open-balena/issues/120
@hedss did similar changes occur to VPN and registry? BTW, to handle this, we'll need to: 1. update open-balena to pass both old and new env vars 2. update open-balena-api...