DNSCrypt Proxy SystemD unit file has no dependencies

[FabrizioMarana]

Who is the bug affecting?

systemd users

What is affected by this bug?

dns-crypt proxy startup

When does this occur?

Boot

Where does it happen?

Here intermittently during boot.

How do we replicate the issue?

Booting the system intermittent error:
Sometimes dnscrypt-proxy service needs to be restarted manually.

Expected behavior (i.e. solution)

Solution:
Include at the top of the DNS-crypt proxy service file the following:

[Unit]
Description=DNS Crypt Proxy
Requires=NetworkManager.target
#After=systemd-logind.service

Why?
Now DNS Crypt Proxy does not have any dependencies and on rare occasions will start before the network is ready. By forcing it to wait until NetworkManager has started, this eliminates the problem.

Other Comments

1. The user that has this issue still has to test. I'll update after that.
2. Not all distro's use NetworkManager, so do some extra digging for Debian and CentOS which might still be using Network service instead of NetworkManager, which will change the dependency.

[jedisct1]

Looks like a duplicate of kardianos/service#77