Re: How to execute an initial script in a container to start the network interface automatically

Laine Stump <laine@xxxxxxxxx> · Thu, 02 Jan 2014 11:21:02 +0200



    On 01/02/2014 05:16 AM, WANG Cheng D
      wrote:

    
        Dear All,
         
        Happy new year to you.
         
        I have a similar
            question which had been replied by Daniel in the following
            post:
         
        http://www.redhat.com/archives/libvir-list/2010-March/msg00296.html
         
        I also want to assign a
            static IP to the container.
         
        As Daniel said, I can
            successfully assign a static IP to the container manually
            using “ # ifconfig eth0 192.168.122.3 netmask 255.255.255.0
            up”.
         
        Daniel also said that we
            can use “the regular distro initscripts” to automatically
            start the network interface, but this doesn’t work on my
            system.
         
        My host is fedora16.
      
    
    I haven't played with lxc enough to answer your question, but you
    *definitely* need to upgrade your Fedora installation - Fedora 16
    has been "out of support" (i.e. no new updates, not even for
    security holes) for almost a year now. Even if you're building your
    own libvirt from source (the 1.0.3 libvirt you're using is newer
    than the last update of libvirt for F16, but still several months
    out of date), the other packages on the system will be extremely out
    of date and likely to cause problems that will never be fixed
    (because no F16 package will ever again be updated).

    
        My libvirtd and virsh
            version is 1.0.3.
         
        
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list