LXC container has no IP - missing dhclient causes ifupdown2 call to fail during start

potatopowered

New Member
Nov 8, 2025
2
0
1
I'm having an interesting problem where one of my LXC has no IP when it starts. The container in question is the proxmox backup server lxc which I'm creating using the community script with default settings. All my other containers and VMs are fine. All my containers use DHCP, and i use the router to reserve fixed IP for each machine. The weird thing is that I first installed this container last week and it got an IP set up fine before I updated proxmox on Fri. Since that update I've had no luck, even when I create a whole new container. I'm hoping someone might be able to help me fix the problem.

After a good amount of troubleshooting I checked the logs with journalctl and found an error configuring eth0 that pointed me to /var/log/ifupdown2, where I found the following in the logs for the most recent start of the container:

Code:
2026-02-09 13:59:42,087: MainThread: ifupdown.dhclient: utilsbase.py:65:read_file_oneline(): debug: reading '/sys/class/net/eth0/carrier'
2026-02-09 13:59:43,087: MainThread: ifupdown: utils.py:301:_log_command_exec(): info: executing /sbin/dhclient -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0
2026-02-09 13:59:43,087: MainThread: ifupdown.dhcp: dhcp.py:217:_up(): error: eth0: cmd '/sbin/dhclient -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0' failed ([Errno 2] No such file or directory: '/sbin/dhclient')

I also tried manually calling dhclient from the command line and it does seem to be missing in the container. I checked my other containers that are working, and they don't seem to be using ifupdown2 at all, and thus are not calling dhclient when initializing the network. Is this missing dhclient something I can/should fix? Or is the container set up by the community script mis-configured in a way that breaks with the latest proxmox update?

Thanks