[BUG] resolveconf mismatch from commit 605d48e

[6jarjar6]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Updated to 605d48e

FROM ghcr.io/linuxserver/baseimage-alpine:edge@sha256:cee81eed536e3077a6658ef3d4471dcdd6fc050009bd26590886b87049a5cc28

My stack failed deployment

rolled back to
FROM ghcr.io/linuxserver/baseimage-alpine:edge@sha256:c9369546a7f37b3dd962de889a7bfffd639cf2e1444664e4663eebb9f4b4a7b7

No issues after reversion

Log output below from container

[2025-07-07T02:17:20+00:00] Connecting...

[#] ip link add dev wg0 type wireguard
[#] 
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 10.5.0.2/32 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] resolvconf -a wg0 -m 0 -x
resolvconf: signature mismatch: /etc/resolv.conf
resolvconf: run resolvconf -u to update
[#] ip link delete dev wg0

Expected Behavior

No response

Steps To Reproduce

1. Using a stack built with https://github.com/6jarjar6/nordlynx
2. Use version of my nordlynx image with 605d48e edge
3. Get error from above

Environment

- OS: Unraid 7.1.4
- How docker service was installed: Built into OS + Portainer

Docker creation

services:
  vpn:
    image: ghcr.io/6jarjar6/nordlynx:latest
    cap_add:
      - NET_ADMIN # Required
      - NET_RAW # Required
    environment:
      - PRIVATE_KEY=REDACTED!!!
      - CONNECT=REDACTED!!!
      - TECHNOLOGY=NordLynx
      - QUERY=REDACTED!!!
      - DNS=1.1.1.1,8.8.8.8,127.0.0.11
      - NETWORK=192.168.1.0/24
      - PERSISTENT_KEEP_ALIVE=25
    ports:
      - 1234:1234
    sysctls:
      - net.ipv6.conf.all.disable_ipv6=0
    restart: always

Container logs

[2025-07-07T02:17:20+00:00] Connecting...

[#] ip link add dev wg0 type wireguard
[#] 
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 10.5.0.2/32 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] resolvconf -a wg0 -m 0 -x
resolvconf: signature mismatch: /etc/resolv.conf
resolvconf: run resolvconf -u to update
[#] ip link delete dev wg0

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[6jarjar6]

I think this package might be the problem

[aptalca]

The commit you linked is for the 3.22 branch, but you're using edge.

Any reason you're using edge? It's not meant for production, and it's at its most unstable state shortly after a new version is released (3.22 just released so edge is now moving fast).

[6jarjar6]

The commit you linked is for the 3.22 branch, but you're using edge.

Any reason you're using edge? It's not meant for production, and it's at its most unstable state shortly after a new version is released (3.22 just released so edge is now moving fast).

For more arch support

I found the root issue

NetworkConfiguration/openresolv#38

I should avoid using edge in my main branch in case others use my image, I will migrate to 3.22 on my stable

[aptalca]

It's this commit that's responsible for that issue: NetworkConfiguration/openresolv@0fdbfd0

[xatier]

Hi, I encountered a similar issue with Podman. You may want to provide a fake signature with your container startup script [1] to cheat openresolv. I hope this helps.

[1] xatier/dockerfiles@9940b1f

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.