Hi,
I installed RocketChat in a docker container. I use it for notifications, so it’s setup in my hass.io configuration.
When the computer reboots, hass.io starts faster than RocketChat, so there is an error saying hass.io couldn’t setup RocketChat platform, which is logical.
So my question is: is there a way, maybe using portainer (which I also installed via the community add-on), to tell docker to wait for RocketChat before running hass.io ?
Hu, ok, but I didn’t install hass.io with compose, so what I am supposed to do with that 
If you don’t use compose, then you are starting them individually. So… start rocketchat, then start hass.io. Or, use compose and then it’ll do it for you in the right order.
I don’t start anything myself, I installed hass.io according to this page (bottom of the page, alternate install).
According to this installer, hass.io containers are controlled by systemd services that call scripts in the /usr/sbin dir, which in turn run the appropriate docker commands.
How about delaying startup of these services ? (hassio-supervisor and hassio-apparmor) Would it be feasible ?
[Edit] It can be done.