(SOLVED) Portainer Add-On does not list running containers, i.e. Sprvisor+related hassio

Configuration
1

Installed the Portainer add-on.
Shows only two containers that I set up, but where are the others that are/must be running given that I am using the core lovelace f/e?

Capture
Capture1920×900 89.6 KB

Here is a list of running containers :-

daz@Pi:~ $ docker ps --all
CONTAINER ID        IMAGE                                              COMMAND                  CREATED             STATUS              PORTS                                                                    NAMES
b43f28d7e528        hassioaddons/portainer-armv7:1.3.0                 "/init"                  12 minutes ago      Up 12 minutes                                                                                addon_a0d7b954_portainer
44029428159f        gpbenton/engmqttclient:1.0.0                       "/opt/energenie_mqtt…"   3 hours ago         Up 3 hours                                                                                   energenie_mqtt_client
bfb6ff71228c        eclipse-mosquitto                                  "/docker-entrypoint.…"   3 hours ago         Up 3 hours          0.0.0.0:1883->1883/tcp, 0.0.0.0:8883->8883/tcp, 0.0.0.0:9001->9001/tcp   mosquitto
c989f2ef25e9        homeassistant/armv7-addon-ssh:8.10.0               "/init"                  11 hours ago        Up 11 hours                                                                                  addon_core_ssh
830a4266ed05        homeassistant/armv7-addon-configurator:5.2.0       "/init"                  11 hours ago        Up 11 hours                                                                                  addon_core_configurator
ec0367ef00a6        hassioaddons/log-viewer-armv7:0.9.1                "/init"                  11 hours ago        Up 11 hours                                                                                  addon_a0d7b954_logviewer
5a926933c439        homeassistant/raspberrypi3-homeassistant:0.118.4   "/init"                  11 hours ago        Up 2 hours                                                                                   homeassistant
025f25a7fbbf        homeassistant/armv7-hassio-multicast:3             "/init"                  12 hours ago        Up 12 hours                                                                                  hassio_multicast
d0f5f5a3bbdc        homeassistant/armv7-hassio-observer:2020.10.1      "/init"                  12 hours ago        Up 12 hours         0.0.0.0:4357->80/tcp                                                     hassio_observer
160ed4f55ea8        homeassistant/armv7-hassio-cli:2020.10.1           "/init /bin/bash -c …"   12 hours ago        Up 12 hours                                                                                  hassio_cli
2fe8895ad2ba        homeassistant/armv7-hassio-audio:17                "/init"                  12 hours ago        Up 12 hours                                                                                  hassio_audio
243f1478f361        homeassistant/armv7-hassio-dns:2020.11.0           "/init"                  12 hours ago        Up 12 hours                                                                                  hassio_dns
60bd9c9865c2        homeassistant/armv7-hassio-supervisor              "/init"                  12 hours ago        Up 11 hours                                                                                  hassio_supervisor
daz@Pi:~ $
2

They are hidden because screwing around with them will likely break your system, also e.g. stopping the core container will shut down your frontend, meaning that you can’t use portainer in Ingress.

Anyway if you really know what you are doing, you can take a look at the hidden containers in Portainer Settings.

1 Like
3

yes, im ok with docker, just wondered why portainer didn’t list them and i see them as hidden
i build my own images :ok_hand:

4

Sorry. Forgot to say THANKS and mark as solved. - Done!

1 Like