From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: Dirk Eibach <dirk.eibach@googlemail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: Kernel tracing from inside a Docker container
Date: Thu, 7 Nov 2024 11:16:14 -0500 [thread overview]
Message-ID: <fe043fc4-b5fc-41ef-83b4-da6c6cfdd0c0@efficios.com> (raw)
In-Reply-To: <CANVMifJ1YQtTkJVop-CmtaDd2+ggU-2n5D6u8Wu3DhKcFER=7Q@mail.gmail.com>
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
> record kernel events.
>
> Thank you so much for your support.
I just looked at the code that loads the modules and we do fail early
if libkmod fails to initialize. I think we could just print a warning
there instead and still try to open '/proc/lttng' and then fail if it's
not present.
next prev parent reply other threads:[~2024-11-07 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 8:03 Dirk Eibach via lttng-dev
2024-11-07 14:27 ` Mathieu Desnoyers via lttng-dev
2024-11-07 14:58 ` Dirk Eibach via lttng-dev
2024-11-07 16:00 ` Dirk Eibach via lttng-dev
2024-11-07 16:16 ` Michael Jeanson via lttng-dev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-07 7:42 Dirk Eibach via lttng-dev
[not found] <9cd16ae1-a2c8-4279-b8df-82ab5be5b31e.9610e98a-1b50-4bc4-83bb-532efa96e9a9.ca90a335-62b6-4541-8ae3-a07498ba9de9@emailsignatures365.codetwo.com>
2024-11-06 7:38 ` Eibach, Dirk via lttng-dev
2024-11-06 15:55 ` Mathieu Desnoyers via lttng-dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe043fc4-b5fc-41ef-83b4-da6c6cfdd0c0@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=dirk.eibach@googlemail.com \
--cc=mjeanson@efficios.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox