I have a third party (Microsoft) that bundles a product (SQL Server 2017) as a
systemd task. Everything pretty much works, but their bundling actually checks if the service is running with
checkrunninginstance.sh which has,
systemctl status mssql-server > /dev/null 2>&1 exit $?
This is problematic because I can't find a way for the container itself to either,
- integrate with the host's copy of systemd, from a chroot
- run as systemd using nspawn
Is it advised for
systemd tasks to use
systemd themselves? If so, how do you do it?