# Full-stack monitoring of stand alone Podman container using --read-only=True option **URL:** \ **Category:** Container platforms\ **Tags:** deep-monitoring, container, podman, oneagent\ **Created:** [March 25, 2024, 1:54pm UTC](https://community.dynatrace.com/t/full-stack-monitoring-of-stand-alone-podman-container-using-read-only-true-option/44842 "2024-03-25T13:54:01Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\ **Post date:** [March 25, 2024, 1:54pm UTC](https://community.dynatrace.com/t/full-stack-monitoring-of-stand-alone-podman-container-using-read-only-true-option/44842/1 "2024-03-25T13:54:01Z")
Hello. Did any one successfully full-stack monitored stand alone Podman (no ~~platform~~ ) containers running with --read-only=True option ? ```auto /usr/bin/podman run ...  --read-only=True ... ``` I have a Linux RHEL host, OneAgent’ed in full-stack mode with Podman container monitoring enabled, running many containers, Ociruntime == crun and Podman version officially supported. But none of my containers are deep monitored. It turns out the use of “--read-only=True” option kind of blocks / disable full-stack monitoring. FYI, on the same host, I deep-monitored sucessfully a container Podman / Tomcat / hello world example. Any experience with this option ? Regards. ---
**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\ **Post date:** [March 28, 2024, 3:30pm UTC](https://community.dynatrace.com/t/full-stack-monitoring-of-stand-alone-podman-container-using-read-only-true-option/44842/2 "2024-03-28T15:30:42Z")
That makes sense as read only will just be reading metrics (Half Stack and Discovery mode) You will need write permissions for Full Stack since it actively injects the JS into your application header. ---
**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\ **Post date:** [March 28, 2024, 3:39pm UTC](https://community.dynatrace.com/t/full-stack-monitoring-of-stand-alone-podman-container-using-read-only-true-option/44842/3 "2024-03-28T15:39:00Z")
Hello. Thanks for feedback. With --read-only=True option I get infra only. Not even “Half Stack”. Object is reported as non monitored or having to be restarted. Also, different (speculative) understanding here : does OneAgent injects on the fly its libraries into the Podman container, so full-stack could work ? Which would require inner-container FS to be writable ? ---
**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\ **Post date:** [March 28, 2024, 3:45pm UTC](https://community.dynatrace.com/t/full-stack-monitoring-of-stand-alone-podman-container-using-read-only-true-option/44842/4 "2024-03-28T15:45:30Z")
Infra is Halfstack 🙂 ---
**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\ **Post date:** [March 28, 2024, 3:47pm UTC](https://community.dynatrace.com/t/full-stack-monitoring-of-stand-alone-podman-container-using-read-only-true-option/44842/5 "2024-03-28T15:47:49Z")
More insight for the discussion. Starting with OneAgent  **1.277.165.20231024-150054+**  bellow hack lead to full-stack monitoring working fine even - with ociruntime == runc (== the default)  - with podman run … --read-only=True … ```auto # In /etc/containers/containers.conf
...
"LD_PRELOAD=/lib64/liboneagentproc.so", ... volumes=[ “/lib64/liboneagentproc.so: /lib64/liboneagentproc.so:ro”, "/opt/dynatrace/oneagent/agent:/opt/dynatrace/oneagent/agent:ro",
... ``` ---
**Author:** ![gilles\_tabary](https://avatars.discourse-cdn.com/v4/letter/g/eb9ed0/32.png) [@gilles\_tabary](https://community.dynatrace.com/u/gilles_tabary)\ **Post date:** [March 28, 2024, 3:49pm UTC](https://community.dynatrace.com/t/full-stack-monitoring-of-stand-alone-podman-container-using-read-only-true-option/44842/6 "2024-03-28T15:49:00Z")
Thanks. Did not know this one. ---
**Author:** ![Stephen1\_Lee](https://avatars.discourse-cdn.com/v4/letter/s/13edae/32.png) [@Stephen1\_Lee](https://community.dynatrace.com/u/Stephen1_Lee)\ **Post date:** [February 24, 2025, 8:30pm UTC](https://community.dynatrace.com/t/full-stack-monitoring-of-stand-alone-podman-container-using-read-only-true-option/44842/7 "2025-02-24T20:30:49Z")
Hi We tried adding the lines above to a containers.conf. But the “LD\_PRELOAD=/lib64/liboneagentproc.so”, causes the following error ERRO[0000] reading system config “/etc/containers/containers.conf”: decode configuration /etc/containers/containers.conf: toml: line 303 (last key “containers”): expected ‘.’ or ‘=’, but got ‘\n’ instead Any idea if there’s another way to use LD\_PRELOAD or is the syntax correct? Thank you