[GH-ISSUE #775] Support for non-systemd linux distributions. #190

New issue

Open

opened 2026-10-13 20:14:58 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-13 20:14:58 +00:00

Owner

Originally created by @KDBal on GitHub (Apr 23, 2024).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/775

Could you, please, make client a bit more distribution-agnostic?

Right now it requires systemd at least for two things:

Service management. It is not a huge problem, since a user can easily create a sysVinit/OpenRC/runit service if needed or even run the service directly.
DNS management. dnsutilslinux uses systemd-resolved, which is a part of systemd. In older versions it just worked with system DNS servers, but now the client does not work at all without systemd-resolved.

Could you, please, add support for openresolv or use some other solution, so that users of non-systemd distributions (like, for example, Gentoo, Alpine, Void, Devuan, Artix, etc.) could still use this software?

Originally created by @KDBal on GitHub (Apr 23, 2024). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/775 Could you, please, make client a bit more distribution-agnostic? Right now it requires systemd at least for two things: 1. Service management. It is not a huge problem, since a user can easily create a sysVinit/OpenRC/runit service if needed or even run the service directly. 2. DNS management. dnsutilslinux uses systemd-resolved, which is a part of systemd. In older versions it just worked with system DNS servers, but now the client does not work at all without systemd-resolved. Could you, please, add support for openresolv or use some other solution, so that users of non-systemd distributions (like, for example, Gentoo, Alpine, Void, Devuan, Artix, etc.) could still use this software?

bsakaguchi commented

2026-10-13 20:14:59 +00:00

Author

Owner

@HojatJoshani commented on GitHub (Sep 16, 2024):

I have the same issue, since I'm using Gentoo Linux.

@HojatJoshani commented on GitHub (Sep 16, 2024): I have the same issue, since I'm using Gentoo Linux.

bsakaguchi commented

2026-10-13 20:14:59 +00:00

Author

Owner

@055110 commented on GitHub (Aug 2, 2025):

Hello, bumping this issue. Using Artix Linux, latest. Its a big shame its being forced to depend on systemD.

@055110 commented on GitHub (Aug 2, 2025): Hello, bumping this issue. Using Artix Linux, latest. Its a big shame its being forced to depend on systemD.

bsakaguchi commented

2026-10-13 20:14:59 +00:00

Author

Owner

@be3d4pb commented on GitHub (Dec 19, 2025):

bump from gentoo+openrc

@be3d4pb commented on GitHub (Dec 19, 2025): bump from gentoo+openrc

bsakaguchi commented

2026-10-13 20:15:00 +00:00

Author

Owner

@Wyrmlet commented on GitHub (Aug 10, 2026):

Bump, Artix Linux. It is still possible to somewhat use the program by making a custom openrc service which starts AmneziaVPN-service in the background, but Amnezia DNS is not functional and some websites fail to resolve because of that.

@Wyrmlet commented on GitHub (Aug 10, 2026): Bump, Artix Linux. It is still possible to somewhat use the program by making a custom openrc service which starts AmneziaVPN-service in the background, but Amnezia DNS is not functional and some websites fail to resolve because of that.

bsakaguchi commented

2026-10-13 20:15:00 +00:00

Author

Owner

@lerothias commented on GitHub (Aug 14, 2026):

Bumping with current state: Gentoo/OpenRC, AmneziaVPN 5.0.0.5.

The service management part is fully workable without systemd — a small OpenRC init script running /opt/AmneziaVPN/bin/AmneziaVPN-service in the background is enough; the client connects via the unix socket /var/run/amneziavpn/daemon.socket.

The remaining blocker is exactly what this issue describes: DNS. On OpenRC, after connecting, DNS resolution breaks and you must manually flush the iptables chain (iptables -F amnvpn.a.310.blockDNS — see #1396). Adding openresolv support, or at least falling back to writing /etc/resolv.conf when systemd-resolved is absent, would be the key fix.

@lerothias commented on GitHub (Aug 14, 2026): Bumping with current state: Gentoo/OpenRC, AmneziaVPN 5.0.0.5. The **service management** part is fully workable without systemd — a small OpenRC init script running `/opt/AmneziaVPN/bin/AmneziaVPN-service` in the background is enough; the client connects via the unix socket `/var/run/amneziavpn/daemon.socket`. The remaining blocker is exactly what this issue describes: **DNS**. On OpenRC, after connecting, DNS resolution breaks and you must manually flush the iptables chain (`iptables -F amnvpn.a.310.blockDNS` — see #1396). Adding `openresolv` support, or at least falling back to writing `/etc/resolv.conf` when `systemd-resolved` is absent, would be the key fix.

bsakaguchi referenced this issue

2026-10-13 20:46:27 +00:00

[PR #190] [MERGED] bugfix/empty-port-when-check-server-ports #1654