[lxc-users] Unable to Load Driver Inside Container

[hari]

Hi Serge,

Thanks for the reply. Could you let me know the steps for clearing the
lxc.cap.drop and setting it with other bits if it's not of inconvenience.
Also do you know which bits should be set?

It is not necessary for me to load the driver inside container. I am not
able to access the driver (which is loaded in the host) inside the
container. I tried the option *lxc-device* (*lxc-device -n <con_name> add
/dev/<dev_name>*) to add the device to the container. It failed to add the
device. If there is a way for the container to use the driver loaded
outside I would be able to get this to work. Any suggestions?

Thanks,
TG

On Tue, Feb 16, 2016 at 7:00 PM, Serge Hallyn <serge.hallyn at ubuntu.com>
wrote:

> Quoting hari (haritg020 at gmail.com):
> > Hi,
> >
> > I have created a container and am trying to load a driver in it. insmod
> is
> > not working and I believe the reason is because of *lxc.cap.drop =
> > sys_module* being set while creating the container. I found this in log
> > though I could not find this setting in any config files. If my
> assumption
> > is right is there any way to unset this or do something like
> *lxc.cap.add =
> > sys_module*?
>
> It's a bad idea to load modules from a container, and if the container is
> in a user ns you will not be able to do it at all.  But if you're sure you
> want to do it  (and you're not in a user ns), then you have to first clear
> lxc.cap.drop and then re-fill it with the other bits.  lxc.cap.drop and
> lxc.cap.add cannot be used together.
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20160217/1a0cc3f6/attachment.html>