Supervised install docs - how to restart, etc. from the host?

[DavidFW1960 (David)]

@rct

Or am I missing something?

I don’t know. Can you read? You have been given a solution many times in this thread but you are ignoring it.

[francisp (Francis)]

@rct

SUPERVISOR_ENDPOINT isn’t set. It does a DNS lookup to the internal DNS running in a container. I didn’t try to look at the go code, but using strace, it connects to the supervisor on port 80 using the container netwo

If ha does a DNS lookup, one of your EXPORT s is missing or wrong.

[kanga_who (Jason)]

@kanga_who

Assuming you are on a PC with Ubuntu/Debian, or a Pi with Raspbian as the base OS, you can install Portainer to manage anything running in Docker.

docker run -d -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

You’ll then access Portainer at YOUR_MACHINE_IP:9000

@kanga_who

The easiest way to stop/start/restart Docker containers is with Portainer.

@paddy0174

I’d advise to now install “Portainer” on the OS level (not in Hass.io). You will now see, which containers are running, stopped and why that is.

@DavidFW1960

USE PORTAINER to start the home assistant container if the supervisor doesn’t. This is the easy way

@rct how many times do you need to have it suggested? USE PORTAINER

[stanwebber]

sorry, i read thru this entire thread and using portainer is not a solution, it is a lazy workaround that requires installing additional software that may or may not be wanted.

the solution is to restart the hass container with docker itself. if that is not working or is inaccessible on the host then that’s an unresolved issue. this is a classic cart before the horse scenario and installing portainer is just buying another horse to pull the cart and the other horse behind it.

[KruseLuds]

Agreed - I have HA Supervised and had to remove portainer to keep it as “supported”