Debian 13 CT Wireguard requires nesting to be disabled

bobbobson

New Member
Oct 1, 2025
4
0
1
as the title says, while Debian 12 Wireguard works fine with nesting=1

steps to reproduce:
apt update && apt upgrade -y
apt install wireguard
nano /etc/wireguard/wg0.conf
systemctl enable --now wg-quick@wg0

on Debian 13 with nesting=1 the systemctl command will hang, sometimes will work if started manually but will fail to start on boot. disabling nesting solves the issue but Debian 12 had no such limitation
 
after testing with the latest debian 12 image "debian-12-standard_12.12-1_amd64.tar.zst" the issue is present here too, so something changed between 12.7 and 12.12 that requires nesting to be disabled for the wireguard service to start correctly
 
Wireguard works fine here before and after upgrading to 13 but I explicitly ran this in the past systemctl disable systemd-networkd-wait-online.
It would wait forever or fail and it looks like I disabled systemd-networkd-wait-online for all my (Debian) containers (but I never got to the root of the problem). Maybe this will help you too?

EDIT: Other people also ran into this: https://forum.proxmox.com/threads/debian-13-lxc-await-network-timeout.169954/ and https://forum.proxmox.com/threads/network-wait-error.143088/
 
Last edited:
  • Like
Reactions: bobbobson
Wireguard works fine here before and after upgrading to 13 but I explicitly ran this in the past systemctl disable systemd-networkd-wait-online.
It would wait forever or fail and it looks like I disabled systemd-networkd-wait-online for all my (Debian) containers (but I never got to the root of the problem). Maybe this will help you too?

EDIT: Other people also ran into this: https://forum.proxmox.com/threads/debian-13-lxc-await-network-timeout.169954/ and https://forum.proxmox.com/threads/network-wait-error.143088/

that seemed to solve it, thanks.