On Mo, 17.05.21 19:08, Marc Weber (marco-owe...@gmx.de) 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
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
> 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
On Mon, May 17, 2021 at 10:20:50AM +0200, Marc Weber wrote:
> Man says:
>
> "
>
> The host system cannot be rebooted and kernel modules may not be
>loaded from within the container.
> "
>
> https://lists.freedesktop.org/archives/systemd-devel/2015-February/027805.html
> said:
>
> "
>
Man says:
"
The host system cannot be rebooted and kernel modules may not be
loaded from within the container.
"
https://lists.freedesktop.org/archives/systemd-devel/2015-February/027805.html
said:
"
We nowadays explicitly disallow non-auto loading of kernel modules
from containers,
