From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: "Eibach, Dirk" <Dirk.Eibach@cloos.de>,
"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: Kernel tracing from inside a Docker container
Date: Wed, 6 Nov 2024 10:55:23 -0500 [thread overview]
Message-ID: <b54eb26d-1818-4c6f-b64d-9b61f02ccc44@efficios.com> (raw)
In-Reply-To: <GV1PR10MB65629CEE94282989CBD614C297532@GV1PR10MB6562.EURPRD10.PROD.OUTLOOK.COM>
Hi,
lttng-modules exposes its control ABI through the
virtual file /proc/lttng.
Does you container have access to that file ?
Note that if you give access to that file within the
container, then the container can observe detailed
information about kernel internals (including related
to other containers).
Thanks,
Mathieu
On 2024-11-06 02:38, Eibach, Dirk via lttng-dev wrote:
> Hi,
>
> I want to do kernel tracing from inside a Docker container.
> Kernel-tracing works from the host and the modules are loaded.
> Userspace tracing works inside the container. But when I do "lttng list
> --kernel" from the container I get "Error: Unable to list kernel events:
> Kernel tracer not available". Running in the container in priviledged
> mode makes no difference.
>
> Mit freundlichen Grüßen / Best Regards
> Dirk Eibach
> _________________________________
> CARL CLOOS SCHWEISSTECHNIK GMBH
> Softwareentwickler / AU-EW
> Softwaredeveloper / AU-EW
> Hauptverwaltung/Headquarters: Carl-Cloos-Strasse 1
> Zentrallager/Central Warehouse: Carl-Cloos-Strasse 6
> 35708 Haiger
> Germany
> Tel: +49 2773 85-888
> E-Mail: mailto:dirk.eibach@cloos.de <mailto:dirk.eibach@cloos.de>
> Internet: http://www.cloos.de/ <http://www.cloos.de/>
>
> Sitz der Firma/Headquarters: 35708 Haiger, Germany
> Amtsgericht/Lower district court: Wetzlar HR B 3052
> UST.-ID-Nr./VAT ID No.: DE 111 79 45 11
> WEEE-Reg.-Nr./WEEE-Reg. No.: DE83919745
> Geschäftsführer/Management: Stephan Pittner (CEO)
>
> <https://www.linkedin.com/company/carl-cloos-schwei%C3%9Ftechnik-gmbh>
> <https://www.youtube.com/user/CloosWelding>
> <https://www.facebook.com/CloosWelding>
> <https://www.instagram.com/CloosWelding>
> <https://www.xing.com/profile/carlcloosschweisstechnikgmbh>
>
> CLOOS-Newsletter <https://www.cloos.de/de-de/#newsletter>
>
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2024-11-06 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2024-11-07 7:42 Dirk Eibach via lttng-dev
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
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=b54eb26d-1818-4c6f-b64d-9b61f02ccc44@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=Dirk.Eibach@cloos.de \
--cc=mathieu.desnoyers@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