Installation on Alpine Linux - DNSCrypt/dnscrypt-proxy GitHub Wiki
Installation on Alpine Linux
Enabling the Community Repository
dnscrypt-proxy is in the 'community' repository, which must be enabled in /etc/apk/repositories by removing the comment # from the appropriate line, e.g.:
# main and community enabled, testing disabled on the 'edge' branch
https://alpine.mirror.wearetriple.com/edge/main
https://alpine.mirror.wearetriple.com/edge/community
#https://alpine.mirror.wearetriple.com/edge/testing
If you're not running on 'edge', then you might see the version numbers instead.
# main and community enabled, testing disabled on the 'V3.9' branch
https://alpine.mirror.wearetriple.com/V3.9/main
https://alpine.mirror.wearetriple.com/V3.9/community
#https://alpine.mirror.wearetriple.com/V3.9/testing
Installation
Alpine Linux maintains its own packages for dnscrypt-proxy and the openrc package for managing the service.
Installation:
apk update && apk add dnscrypt-proxy dnscrypt-proxy-openrc
Service Setup
To start at boot, use:
rc-update add dnscrypt-proxy default
Then, to start the service immediately:
rc-service dnscrypt-proxy start
or
/etc/init.d/dnscrypt-proxy start
Files
Configuration of the /etc/dnscrypt-proxy/dnscrypt-proxy.toml file is discussed elsewhere on this wiki.
There are also some examples in the Alpine package sources.
Example configuration files are stored in /usr/share/dnscrypt-proxy.
Upgrades
When upgrading the package, a new file /etc/dnscrypt-proxy/dnscrypt-proxy.toml.apk-new will be created.
The original configuration file remains, and the new default configuration file gets this apk-new extension.
Be aware that new configuration properties (if available) will be in the apk-new file, since an edited configuration file cannot be automatically updated.
To see the differences, use the diff command:
diff /etc/dnscrypt-proxy/dnscrypt-proxy.toml /etc/dnscrypt-proxy/dnscrypt-proxy.toml.apk-new