[BUG] Setting SERVER_ALLOWEDIPS_PEER_ does not recreate configs

[rwrnet]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

If you set the ENV SERVER_ALLOWEDIPS_PEER_... peer configs are not recreated.

Log also states: **** No changes to parameters. Existing configs are used. ****

This is due to:

docker-wireguard/root/etc/s6-overlay/s6-rc.d/init-wireguard-confs/run

Line 178 in 095f857

if [[ "$SERVERURL" != "$ORIG_SERVERURL" ]] || [[ "$SERVERPORT" != "$ORIG_SERVERPORT" ]] || [[ "$PEERDNS" != "$ORIG_PEERDNS" ]] || [[ "$PEERS" != "$ORIG_PEERS" ]] || [[ "$INTERFACE" != "$ORIG_INTERFACE" ]] || [[ "$ALLOWEDIPS" != "$ORIG_ALLOWEDIPS" ]] || [[ "$PERSISTENTKEEPALIVE_PEERS" != "$ORIG_PERSISTENTKEEPALIVE_PEERS" ]]; then

not checking for changes on the SERVER_ALLOWEDIPS_PEER Envs.

Expected Behavior

If one adds a SERVER_ALLOWEDIPS_PEER_... config is being recreated.

Steps To Reproduce

1. start a fresh server config
2. add SERVER_ALLOWEDIPS_PEER_... for one of the peers
3. recreate pod
4. check for allowedip config added to wg0.conf

Environment

- OS: Ubuntu 24.04
- How docker service was installed: via apt install docker-ce

CPU architecture

x86-64

Docker creation

It should be reproducible with every config. Happy to provide my anonymized specific one, in case it is needed.

Container logs

**** Server mode is selected ****
**** No changes to parameters. Existing configs are used. ****

[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.

[rwrnet]

Just realized, that the documentation states this explicitely. Closing issue.