go to “Containers” in the left menu. Then click on the container you want to log into. Then from there in the top section at the bottom there will be 4 choices. The third is “Console”. That’s the one you want.
Or in the “Containers” page you can use the third icon and it takes you to the same place. It’s just not labeled.
I would have thought that you would have more containers than that show up there. On my system the HA Supervised install creates 7 containers (along with all of the containers for each add-on):
Granted I’m on a Debian machine (not HASSOS) but my understanding is that it shouldn’t make any difference as far as Portainer showing all of the containers.
the container you want should be the “homeassistant” container.
well, on a non-production system I first "removed’ a non vital container, and indeed it immediately popped up listed in the containers. So, I tried to remove the homeassistant and checked, but it has vanished…grr
Maybe We (I) should take this to a separate thread, because this is more of a ‘How to install the test tool’ thread than about actual cpu usage.
It is likely an integration that has a run away thread / loop.
Keeping taking py-spyrecords each time it happens. Sometimes you have to compare 4 or 5 of them against the idle ones to see the pattern. Make sure to take a py-spydump as well as it will show the threads.
You may have some luck with strace as well. If you can figure out which thread is running away and attach to it (you can use the py-spydump output to narrow it down)