Hi @Filippo-GEG
I’ve observed no problem on my side.
Just a major question : did you attach (exec) to your running container before launching the top command ?
torizon@verdin-imx8mp-15229850:~$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bf374bd6f1e9 192.168.0.65:5002/avalonia-ui-the-series-fb-drm:arm64 "/usr/sbin/sshd -D" 2 hours ago Up 2 hours torizon-avalonia-ui-the-series-fb-drm-debug-1
torizon@verdin-imx8mp-15229850:~$ docker exec -it bf374bd6f1e9 /bin/bash
root@verdin-imx8mp-15229850:/# top
top - 15:35:20 up 3 days, 9:23, 0 user, load average: 0.08, 0.10, 0.09
Tasks: 8 total, 1 running, 7 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 0.6 sy, 0.0 ni, 99.2 id, 0.0 wa, 0.2 hi, 0.1 si, 0.0 st
MiB Mem : 3922.1 total, 1504.9 free, 963.0 used, 1676.9 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 2959.2 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
25 torizon 20 0 260.4g 169268 81036 S 6.3 4.2 7:04.43 AvaloniaUITheSe
14 torizon 20 0 3463864 171240 75928 S 0.3 4.3 0:37.75 Command Thread
79 root 20 0 9004 4444 2548 R 0.3 0.1 0:00.02 top
1 root 20 0 16328 8644 7352 S 0.0 0.2 0:00.09 sshd
6 root 20 0 19196 9732 8204 S 0.0 0.2 0:00.06 sshd
12 torizon 20 0 19456 6576 4784 S 0.0 0.2 0:00.36 sshd
13 torizon 20 0 2316 812 728 S 0.0 0.0 0:00.00 sh
73 root 20 0 4472 3400 2928 S 0.0 0.1 0:00.05 bash
I think that you did not attach to your running container because you see all the processes of the OS.
Can you verify that you’er attached to your running container, because this would explain that you cannot see your process since it is running inside your container and therefore not visible outside.
Please, let me know.
Sincerely,
François.