How to prevent network config in lxc from being overwritten

[alitvak69]

Dear all,

I am trying to add multiple IP addresses inside the lxc container. I know that there are multiple methods, but the one I am looking for is to add extra IP address from within the container using standard network settings of guest OS.

PCT seems to overwrite ifcfg-eth0 static IP config in my centos7 container no matter what I use. I know that running lxc on ubuntu server with centos containers doesn't cause the issue. I can add several IP addresses to a single interface within the container and even if lxc container config has network settings it doesn't rewrite my cfg file.

Any way to achieve the same with containers in proxmox ?

 

[LnxBil]

There are several ways to do this, yet the only that will work with your way is to set the configuration file immutable.

 

[alitvak69]

There are several ways to do this, yet the only that will work with your way is to set the configuration file immutable.

How do I do that ?

 

[LnxBil]

http://bfy.tw/6tFc

 

[fabian]

you can "touch /etc/network/.pve-ignore.interfaces" to tell PVE to not change that file.

 

[elBradford]

There are several ways to do this, yet the only that will work with your way is to set the configuration file immutable.

Making the file immutable did not fix the issue - in fact, it made it worse. The container refused to boot when that file is immutable.

 

[elBradford]

you can "touch /etc/network/.pve-ignore.interfaces" to tell PVE to not change that file.

This solved it for me and allowed me to use a post-up command to configure the interface for snort.

 

[alitvak69]

Thank you all.

 

[fotisevangelou]

you can "touch /etc/network/.pve-ignore.interfaces" to tell PVE to not change that file.

Is there any equivalent trick for Red Hat based OSs (CentOS 7 in particular) where the path to the interfaces is "/etc/sysconfig/network-scripts"?

Thank you.

 

[fotisevangelou]

As a sidenote, let me add that after a reboot, networking is lost and the container's external IP is the Promox server's IP. But if I do "ifdown eth0 && ifup eth0" right after the reboot, the container will then pick up the correct networking configuration.

 

[fabian]

Is there any equivalent trick for Red Hat based OSs (CentOS 7 in particular) where the path to the interfaces is "/etc/sysconfig/network-scripts"?

Thank you.

PVE should not touch any file in the container for which a .pve-ignore. file exists, see PVE Admin Guide

 

[fotisevangelou]

Thank you @fabian

 

[cj_duke]

Dear all,

apologies for bringing this thread up again.

I'm setting up a container (ubuntu-20.04) with a specific network setup, therefore I would like to use .pve-ignore on the network config of the container. Unfortunately /etc/network/.pve-ignore.interfaces does not seem to work with ubuntu-20.04 container. Could anyone please help me where to put .pve-ignore.interfaces in the container, so that the network config is not set up by the host?

Thank you for your help.

 

[H4R0]

Dear all,

apologies for bringing this thread up again.

I'm setting up a container (ubuntu-20.04) with a specific network setup, therefore I would like to use .pve-ignore on the network config of the container. Unfortunately /etc/network/.pve-ignore.interfaces does not seem to work with ubuntu-20.04 container. Could anyone please help me where to put .pve-ignore.interfaces in the container, so that the network config is not set up by the host?

Thank you for your help.

ubuntu uses netplan not network, /etc/netplan/.pve-ignore.config.yaml

 

[cj_duke]

ubuntu uses netplan not network, /etc/netplan/.pve-ignore.config.yaml

Works, thank you very much.