[lxc-users] Ubuntu 14 Container Fedora 20 ignoring most NICs

[CDR]

Same compilation error under Fedora 20.
By any chance do you have a workaround?
I need to replace a physical server and I need a red-hat compatible container.

Checking for unpackaged file(s): /usr/lib/rpm/check-files
/root/rpmbuild/BUILDROOT/lxc-1.1.0-0.1.alpha1.fc20.x86_64
error: Installed (but unpackaged) file(s) found:
   /usr/lib/systemd/system/lxc-net.service


RPM build errors:
    File listed twice:
/usr/lib64/python3.3/site-packages/_lxc-0.1-py3.3.egg-info
    File listed twice: /usr/lib64/python3.3/site-packages/_lxc.cpython-33m.so
    File listed twice: /usr/lib64/python3.3/site-packages/lxc/__init__.py
    File listed twice: /usr/lib64/python3.3/site-packages/lxc/__pycache__
    File listed twice:
/usr/lib64/python3.3/site-packages/lxc/__pycache__/__init__.cpython-33.pyc
    File listed twice:
/usr/lib64/python3.3/site-packages/lxc/__pycache__/__init__.cpython-33.pyo
    File listed twice: /usr/libexec/lxc/lxc-autostart-helper
    File listed twice: /usr/libexec/lxc/lxc-devsetup
    File listed twice: /usr/libexec/lxc/lxc-user-nic
    Installed (but unpackaged) file(s) found:
   /usr/lib/systemd/system/lxc-net.service
make: *** [rpm] Error 1



On Fri, Sep 5, 2014 at 1:39 PM, CDR <venefax at gmail.com> wrote:
> Same issue, it only shows eth0 and eth1. no error
> I thing the container
> I tried to compile LXC in Centos 7, so I could make a  container, but
> compilation fails. I already reported the issue to the development
> list.
> In Ubuntu 14.04, I created a new centos 7 container, fro downloadable
> templates, but after a successful creation, it does not start  and it
> does not even give me an error message using --logfile
> I am caught between a rock and a hard-place, it seems.
>
>
> On Fri, Sep 5, 2014 at 1:21 PM, Serge Hallyn <serge.hallyn at ubuntu.com> wrote:
>> Quoting CDR (venefax at gmail.com):
>>> I have a Fedora 20 container with 10 nics
>>>  lspci -bv | grep -i ethernet -A1
>>
>> If it is a container, then lspci output has nothing to do with what is
>> in the container.  If the host has 10 nics and you want to pass them
>> into the container, then do so with lxc.network.type = phys entries.
>>
>>
>> _______________________________________________
>> lxc-users mailing list
>> lxc-users at lists.linuxcontainers.org
>> http://lists.linuxcontainers.org/listinfo/lxc-users