AMD uProf Power Profiler can be used for system wide profiling and for application profiling inside the docker environment. This support is only on Linux platforms.
To run the Power Profiler in the docker environment, begin by installing the Power Profiler driver inside the container.
By default, docker containers have their own isolated PID namespace, which means they do
not see processes outside their own container. If your application needs visibility into
processes outside the container (such as host processes), you can run the container in
the host PID namespace using the
--pid=host option when starting the
container.sudo docker run --pid=host <image>AMD uProf CPUProfiler can be used for analysis of applications running inside the Docker container environments. This is supported only on Linux platforms. Choose one of the following approaches for application analysis:
- Run AMD uProf inside the Docker container to analyze the application.
CAP_SYS_ADMIN permission (
docker run --cap-add=CAP_SYS_ADMIN) is required to enable profiling. Both CLI and GUI based profiling and analysis are supported in this mode. - Run AMD uProf CLI outside the Docker container to profile and analyze the
target application running in the container:
- Attach uProf CLI to the containerized process using the
--pidoption during collection. Alternatively, collect the system-wide data and filter by PID during report generation. - During report generation, provide the path to the binary and source code
(
--bin-pathand--src-path) of the profiled application running in the container. AMD uProf GUI doesn't support profiling and analysis in this mode.
- Attach uProf CLI to the containerized process using the