Comment 2 for bug 1821788

This is not a bug exactly because what happens is that the service fails to start, and thus the install is aborted.

The solution here is to use the install hook to disable the service as the install hook runs before the services are started, and we no longer start services which have been disabled from the install hook. Then in the post-connect hook you can restart the service.

We may eventually enable a way for a service to be declared as initially disabled in the snapcraft.yaml, but this is not on our current roadmap.