[SOLVED] CentOS Container network not starting

motoboy82

New Member
Mar 19, 2015
3
0
1
Problem: Can't bring up network in container. CentOS scripts would fail with error that IP address is already in use. The OS scripts on this distribution do some checking which might be environment specific to me but regardless i'm smart enough to assign IP addresses that are not already in use so this is not something want an OS failing to bring up an interface on a false positive.

I don't know if this helps anyone else but hopefully it does. If it's recommended that I file a bug report let me know i'm happy to do so.

Container Type: LXC
Container OS: CentOS 7
ProxMox Version 4 updated to latest w/ apt-get update && upgrade

The site (because i'm new) won't let me post the patch file i made to fix the problem. But I can describe it so if someone else has this problem you will know what you need to do.

Solution: add 2 $data .= "ARPCHECK=no\n"; lines to /usr/share/perl5/PVE/LXC/Setup/Redhat.pm. One is for the IPV4 check, the other for IPV6. with the container OS not doing the ARP check the interfaces come up as normal and there are no problems. This was important as now I fixed the GUI/<ID>.conf network settings they would overwrite my custom config and it wouldn't come up without this check disabled. the line was added after setting the manual IPV4/6 addresses.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!