rebase to 3.23

[aptalca]

testing locally

Tested locally with 2 wireguard containers on 2 different VPSes:

• Set first one up with PEER=1, PEERDNS=auto, INTERNAL_SUBNET=10.13.18.0 and URL=mydomain.duckdns.org
• Set the second one up with no env vars and the conf from first server dropped in (contains DNS = 10.13.18.1)
• Started the second container, it connects to the first via duckdns domain:
  • wg show on the first shows the handshake
  • wg show on the second shows the first one's IP in endpoint (correct url resolution)
  • curl icanhzip.com on the second returns the first one's IP
  • resolv.conf contains the header # Generated by resolvconf and nameserver 10.13.18.1
  • Exec'ed in and did wg_quick down wg1, resolv.conf contents reverted to docker default with my host's search domains
• Then removed the conf from the second and restarted with an invalid conf, resolv.conf was docker's original with my search domains, but with the header added # Generated by resolvconf

PS.
I also noticed that the init script fails with a confusing message if no wg conf is supplied:

**** Found WG conf /config/wg_confs/*.conf, but it doesn't seem to be valid, skipping. ****
**** No valid tunnel config found. Please create a valid config and restart the container ****

We should probably check for that condition and log a message, but that can be in a different PR.

[LinuxServer-CI]

I am a bot, here is the pushed image/manifest for this PR:

ghcr.io/linuxserver/lspipepr-wireguard:1.0.20250521-r1-pkg-1e8578fc-dev-0b19f44326665d275ca466f4e454d95331ce3649-pr-402

[LinuxServer-CI]

I am a bot, here is the pushed image/manifest for this PR:

ghcr.io/linuxserver/lspipepr-wireguard:1.0.20250521-r1-pkg-1e8578fc-dev-ad124609248ce6aff978110e28d5ac9b97049be4-pr-402