Closed SURAJTHEGREAT closed 3 years ago
I am refering to this link to host a DNS server with dnscrypt service : https://github.com/DNSCrypt/dnscrypt-proxy/wiki/How-to-setup-your-own-DNSCrypt-server-in-less-than-10-minutes.
One of the steps mentioned is execute below to auto restart if the VM is rebooted
docker update --restart=unless-stopped dnscrypt-server
But unfortunately on reboot , the below exception is thrown.
ln: failed to create symbolic link '/etc/runit/runsvdir/svmanaged/unbound': File exists
I am using the latest image (https://hub.docker.com/r/jedisct1/dnscrypt-server)
Follow the steps as in wiki https://github.com/DNSCrypt/dnscrypt-proxy/wiki/How-to-setup-your-own-DNSCrypt-server-in-less-than-10-minutes
To restart without this error ln: failed to create symbolic link '/etc/runit/runsvdir/svmanaged/unbound': File exists
I am refering to this link to host a DNS server with dnscrypt service : https://github.com/DNSCrypt/dnscrypt-proxy/wiki/How-to-setup-your-own-DNSCrypt-server-in-less-than-10-minutes.
One of the steps mentioned is execute below to auto restart if the VM is rebooted
docker update --restart=unless-stopped dnscrypt-server
But unfortunately on reboot , the below exception is thrown.
ln: failed to create symbolic link '/etc/runit/runsvdir/svmanaged/unbound': File exists
I am using the latest image (https://hub.docker.com/r/jedisct1/dnscrypt-server)
Follow the steps as in wiki https://github.com/DNSCrypt/dnscrypt-proxy/wiki/How-to-setup-your-own-DNSCrypt-server-in-less-than-10-minutes
To restart without this error ln: failed to create symbolic link '/etc/runit/runsvdir/svmanaged/unbound': File exists