Re: manually lading kernel modules and have created /dev/* in container?

[Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>]

On Mon, May 17, 2021 at 07:08:55PM +0200, Marc Weber wrote:
> > devtmpfs
> 
> thanks. So I can modprobe (-r) the modules from both host/container,
> 
> eg dahdi_transcode makes /dev/dahdi/transcode appear.
> 
> But when mounting from container I can write / read from it (getting errors
> 
> about channels not setup which is probably expected), but I when trying same from the container I
> 
> just get operation not permitted. chmod 777 or such doesn't help.
> 
> I am not using UID/-U id rewriting in any way. I run the container with --capability=all.
> 
> Is there something else I am missing ?

Sounds like you need to ask about this with whatever framework your
"containers" are being created with.  It's not a systemd issue here, and
as the kernel is working properly, doesn't seem to be a kernel issue
either.

Your "containers" are probably set to not allow access to these device
nodes, and rightly so, as that's not normally a good thing to allow.

good luck!

greg k-h
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel