On Mon 2020-10-12 09:35:56 +0200, Jack Henschel wrote: > I also just ran into this issue yesterday. > I installed `wireguard-tools` on a minimal Debian Buster system and > `wg-quick` gave me the same error: > >> wg-quick up wg0 >> ... >> >> [#] resolvconf -a wg0 -m 0 -x >> /usr/bin/wg-quick: line 32: resolvconf: command not found > > Is there a particular reason why `wireguard-tools` only "suggests" resolvconf > but does not depend on it? > From my point of view, resolvconf should be a hard dependency. > > As mentioned before, installing the `resolvconf` package fixed the issue.
Some users of wireguard-tools may never need to use wg-quick (e.g. they
might just use /usr/bin/wg)
Or, if they do use wg-quick, they might not use it with a configuration
that tries to adjust the system resolvers.
Finally, the resolvconf interface might be supplied by a number of
different implementations -- either resolvconf, openresolv, or
systemd-resolved's alias of resolvectl could be the relevant
implementations.
please see #930735 for more discussion.
--dkg
signature.asc
Description: PGP signature
