Container loosing ip every 12hrs after removing 2nd eth adapter

[daves_nt_here]

I had a container running Apache with 2 networks on it.
I have since split up those containers up.
Container 1 (original) - removed eth1 and kept eth0
Container 2 (cloned) - removed eth0 and renamed eth1 to eth0 keeping the eth1 mac address

Since doing this, both containers loose ip every 12hrs. After rebooting things work as expected.

Why is eth1 still showing up when the DHCP is being renewed?
I have checked the conf file and only eth0 is in their: net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=02:7B:D1:59:9F:A4,ip=dhcp,type=veth


The following log is from container 1 that I had removed eth1.

Feb 01 09:33:42 Apache dhclient[70]: Internet Systems Consortium DHCP Client 4.4.1
Feb 01 09:33:42 Apache ifup[70]: Internet Systems Consortium DHCP Client 4.4.1
Feb 01 09:33:42 Apache ifup[70]: Copyright 2004-2018 Internet Systems Consortium.
Feb 01 09:33:42 Apache ifup[70]: All rights reserved.
Feb 01 09:33:42 Apache ifup[70]: For info, please visit https://www.isc.org/software/dhcp/
Feb 01 09:33:42 Apache ifup[70]: Listening on LPF/eth0/02:7b:d1:59:9f:a4
Feb 01 09:33:42 Apache ifup[70]: Sending on   LPF/eth0/02:7b:d1:59:9f:a4
Feb 01 09:33:42 Apache ifup[70]: Sending on   Socket/fallback
Feb 01 09:33:42 Apache ifup[70]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Feb 01 09:33:42 Apache ifup[70]: DHCPOFFER of 192.168.55.29 from 192.168.55.1
Feb 01 09:33:42 Apache ifup[70]: DHCPREQUEST for 192.168.55.29 on eth0 to 255.255.255.255 port 67
Feb 01 09:33:42 Apache dhclient[70]: Copyright 2004-2018 Internet Systems Consortium.
Feb 01 09:33:42 Apache dhclient[70]: All rights reserved.
Feb 01 09:33:42 Apache dhclient[70]: For info, please visit https://www.isc.org/software/dhcp/
Feb 01 09:33:42 Apache dhclient[70]:
Feb 01 09:33:42 Apache dhclient[70]: Listening on LPF/eth0/02:7b:d1:59:9f:a4
Feb 01 09:33:42 Apache dhclient[70]: Sending on   LPF/eth0/02:7b:d1:59:9f:a4
Feb 01 09:33:42 Apache dhclient[70]: Sending on   Socket/fallback
Feb 01 09:33:42 Apache dhclient[70]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Feb 01 09:33:42 Apache dhclient[70]: DHCPOFFER of 192.168.55.29 from 192.168.55.1
Feb 01 09:33:42 Apache ifup[70]: DHCPACK of 192.168.55.29 from 192.168.55.1
Feb 01 09:33:42 Apache dhclient[70]: DHCPREQUEST for 192.168.55.29 on eth0 to 255.255.255.255 port 67
Feb 01 09:33:42 Apache dhclient[70]: DHCPACK of 192.168.55.29 from 192.168.55.1
Feb 01 09:33:42 Apache dhclient[70]: bound to 192.168.55.29 -- renewal in 18610 seconds.
Feb 01 09:33:42 Apache ifup[70]: bound to 192.168.55.29 -- renewal in 18610 seconds.
Feb 01 09:33:42 Apache dhclient[108]: Internet Systems Consortium DHCP Client 4.4.1
Feb 01 09:33:42 Apache ifup[108]: Internet Systems Consortium DHCP Client 4.4.1
Feb 01 09:33:42 Apache ifup[108]: Copyright 2004-2018 Internet Systems Consortium.
Feb 01 09:33:42 Apache ifup[108]: All rights reserved.
Feb 01 09:33:42 Apache ifup[108]: For info, please visit https://www.isc.org/software/dhcp/
Feb 01 09:33:42 Apache dhclient[108]: Copyright 2004-2018 Internet Systems Consortium.
Feb 01 09:33:42 Apache dhclient[108]: All rights reserved.
Feb 01 09:33:42 Apache dhclient[108]: For info, please visit https://www.isc.org/software/dhcp/
Feb 01 09:33:42 Apache dhclient[108]:
Feb 01 09:33:42 Apache ifup[116]: Cannot find device "eth1"
Feb 01 09:33:42 Apache dhclient[108]: Failed to get interface index: No such device
Feb 01 09:33:42 Apache ifup[108]: Failed to get interface index: No such device
Feb 01 09:33:42 Apache ifup[108]: If you think you have received this message due to a bug rather
Feb 01 09:33:42 Apache ifup[108]: than a configuration issue please read the section on submitting
Feb 01 09:33:42 Apache ifup[108]: bugs on either our web page at www.isc.org or in the README file
Feb 01 09:33:42 Apache ifup[108]: before submitting a bug.  These pages explain the proper
Feb 01 09:33:42 Apache ifup[108]: process and the information we find helpful for debugging.
Feb 01 09:33:42 Apache ifup[108]: exiting.
Feb 01 09:33:42 Apache dhclient[108]:
Feb 01 09:33:42 Apache dhclient[108]: If you think you have received this message due to a bug rather
Feb 01 09:33:42 Apache dhclient[108]: than a configuration issue please read the section on submitting
Feb 01 09:33:42 Apache dhclient[108]: bugs on either our web page at www.isc.org or in the README file
Feb 01 09:33:42 Apache dhclient[108]: before submitting a bug.  These pages explain the proper
Feb 01 09:33:42 Apache dhclient[108]: process and the information we find helpful for debugging.
Feb 01 09:33:42 Apache dhclient[108]:
Feb 01 09:33:42 Apache dhclient[108]: exiting.
Feb 01 09:33:42 Apache ifup[51]: ifup: failed to bring up eth1
Feb 01 09:33:42 Apache systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Feb 01 09:33:42 Apache systemd[1]: networking.service: Failed with result 'exit-code'.
Feb 01 09:33:42 Apache systemd[1]: Failed to start Raise network interfaces.

 

[daves_nt_here]

After a good day of Googling, I found a reference to the interface file inside the LXC (/etc/network/interfaces)
Looks like Proxmox will not clean up this file if you remove an interface from the network GUI tab.
The container was attempting to renew my DHCP on all the interfaces listed inside this file and since eth1 didn't exist anymore it couldn't refresh the IP thus crashing the container. After removing eth1 from the interfaces file, everything is running smoothly again.