How to start the linux container's network interface automatically

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear all,

 

I failed to start the linux container's network interface automatically. I have to start it manually each time after the container finishes booting.

 

I know that in a native fedora, if we want the network interface to start automatically, we should edit "/etc/sysconfig/network-script/ifcfg-eth0 and add the string "_ONBOOT_=yes".

 

My host is fedora 16. I used “yum --installroot=/root/fedoralxc --releasever=16 install -y openssh, bridge-utils” to setup the rootfs for my container (Laine thought that my fedora version is a little bit older, I wonder if the newer version fedora container can automatically start its network interface )

 

After rootfs installation, in the container's file system, there is no sub-directory named “network-scripts” in “/etc/sysconfig” . So, I created this directory manually and added a file named “ifcfg-eth0”, but the container's network interface still cannot start automatically.

 

I tried to add files “.bash_profile” and “.bashrc” in which I added the “ifconfig” in the shell script to try to configure eth0 automatically, but it still doesn’t work.

 

I wonder if there is a “.bashrc” for the root of a container? If there is, where should this file be located?

 

Any comments will be highly appreciated.

 

Cheng

 

_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users

[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux