On 2024-11-07 03:03, Dirk Eibach via lttng-dev wrote:
Hi,
sorry, Outlook is messing up my plaintext mails, so I am switching to
my gmail account.
lttng-modules exposes its control ABI through the virtual file /proc/lttng.
Does you container have access to that file ?
The container is runnin
Hi,
I guess I found it! The kernel module files have to be present under
/lib/modules inside the container, even when they are already loaded
on the host side.
After putting them there, everything works fine and I finally can
record kernel events.
Thank you so much for your support.
Regards
Dirk
Hi,
sorry, Outlook is messing up my plaintext mails, so I am switching to
my gmail account.
> lttng-modules exposes its control ABI through the virtual file /proc/lttng.
>
> Does you container have access to that file ?
The container is running in privileged mode.
root@9348eb19e6f4:/# ls -l /pro
Hi Mathieu,
> 1) You modprobe all LTTng modules from your top level namespace (host
> system) before starting lttng-sessiond within the container, or
since I already did a lttng session on the host/top level namespacer
the modules are already loaded:
root@9348eb19e6f4:/# lsmod
Module
On 2024-11-07 11:00, Dirk Eibach via lttng-dev wrote:
> Hi,
>
> I guess I found it! The kernel module files have to be present under
> /lib/modules inside the container, even when they are already loaded
> on the host side.
> After putting them there, everything works fine and I finally can
> reco
Hi,
sorry, Outlook is messing up my plaintext mails, so I am switching to
my gmail account.
> lttng-modules exposes its control ABI through the virtual file /proc/lttng.
>
> Does you container have access to that file ?
The container is running in privileged mode.
root@9348eb19e6f4:/# ls -l /pro
