home assistant docker restart

You should NOT have to do that. You still need to modify and then re-run your docker run commands but at least Portainer simplifies part of it. I do use Portainer to manage my docker environment but use compose to run up and update. Restarting the supervisor only restarts the supervisor itself (which might be useful for checking for updates). For exapmle, work just fine, but when container is created without --restart=unless-stopped and service (systemctl) is created to start and stop hass container it fails as shown in first code window. This file has been truncated. Hassio is great to get started but I may move away to a Home Assistant installation to gain more flexibility. Now you can decide between two methods, only install HA, meaning only HomeAssistant is installed, no addOns, no managing outside HA. The supervisor image version is 201, Operating environment (HassOS/Generic): sudo docker restart homeassistant (or whatever the container name is). First, your error is related to your install. To do that you have 2 options. Actually Im just curious why this happen. if supervisor is not running, you need to try. Also, I see that there's a "repair" function in /usr/src/hassio/hassio/homeassistant.py that looks like it forces an install, and the install functions cause the docker start to occur. You have a few possible installation methods with HA, depending on what you want later. You can install the HA cli to run an bare metal, without the hassio ssh add-on. Added MQTT (which I had running on a separate PI before), Grafana and influxdb. According to the help for that script, "host reboot" means rebooting my Linux box. environment: I never want to shotgun an update of all containers, or a start/stop of all containers. Install Portainer with the code I listed in my previous post. Use Portainer to remove the existing container. systemctl restart hassio-supervisor.service, I found if you install HassOs, at least the 64-bit VM, it gets unstable & need a reboot. However I would definitely use docker-compose. Id like to add restart always and the location of my usb stick device /dev/ttyACM0. And I dont run anything before after etc. That seems super weird. So, this is about Home Assistant Supervised or Home Assistant OS? and here https://www.home-assistant.io/hassio/commandline/. Alternatively, you can do the same from the command line, but Portainer has a nice web interface that makes it super easy. container_name: hassio_supervisor Read up on it, youll find the format for docker-compose.yml files very familiar to what you do in homeassistant. Why would rebooting my linux box be required just to get the homeassistant instance restarted? systemctl stop hassio-supervisor appears to stop the supervisor docker container, but it leaves the other containers running hassio-audio, hassio-dns, homeassistant, and add-ons. Already on GitHub? I can confirm that there is something wrong with supervisor. In my personal opinion as a former Unix administrator, I think HassOs is likely unstable. I do run Home Assistant Container (and others) on both - Raspbian and Ubuntu - and all containers having restart policy allways are (re-) started as soon as the Docker service is restarted by systemd. It does a DNS lookup to the internal DNS running in a container. The homeassistant container starts correctly at boot. My point, when supervisor is running, but homeassistant is not , the ha CLI wont work. Yes, the only way to fix that is with the ha supervisor repair command, After this is implemented, you have an CLI also with superviserd installations: ( Do not mind MQTT error - mqtt container not running ) My suggestion would be to take a look at the Docker documentation and get at least the basics for Docker. Youll then access Portainer at YOUR_MACHINE_IP:9000. Also, doesnt the availability of the ssh add-on container depends on supervisor running correctly? https://hub.docker.com/r/portainer/portainer. Havent looked at apparmor yet. The local installed part on your host will prevent that and also care that he shutdown/startup correctly on boot. A restart, and all is well again, but I find that just starting it from within HassIO is not sufficient and it really needs the whole docker environment restarted. But with that said, if your HA really hangs this wont work, then the automations wont run anyway. The mount point has to be /config, so that Home Assistant will use it for the configs and logs. That means, your containers cant talk to each other and there is no container who takes the lead (=host). **. You will now see, which containers are running, stopped and why that is. Install Portainer. command, it it possible. ), anyone knows what that means in different behaviour (do not understand much about docker), Actually no, just now it got stuck, I did the restart as per the POST URL, and did not work (it worked before), so I had to do a sudo docker restart homeassistant, and it worked, So I need a way to give easily the Hmm, I just tried that on a regular Hass.io (fully hassos image), the ha command works without homeassistant running. I dont think the supervisor has its own endpoint, yet? But. Instead of managing the compose file on your own, you interact with it and deploy it through portainer. Anyone looking at jumping into this pond, it was pretty straight forward. Go to the sidebar -> Configuration -> Server Controls -> Restart, I cant anything from the GUI if homeassistant isnt running. --device not allowed. I figured that out right away when I looked to see what systemd unit files got installed. ha-dockermon Here's the logs, and I'll show you the problem: The problem is that those docker instances are not, in fact, running! Powered by Discourse, best viewed with JavaScript enabled. add the exports to /etc/profile at the bottom !!! But also the systemd will care that the supervisor is shutdown correctly. Learn more about Reddits use of cookies. :tractor: Hass.io build tools. Supervisor and Homeassistant are both containers. Do not use unless-stopped as the container of course is stopped during shutdown. I use compose to get portainer running on a fresh install, but then use stacks to get the rest up. I've been struggling with what I think is the same problem with perhaps a few different details. homeassistant). I get it, that this is no longer a recommended install and am trying to move to docker. I believe these are responsible for starting the containers at boot. As andygrunwald said, that issue doesn't really explain what the goal is. Youre looking for Sudo docker stop/start , Home Assistant is open source home automation that puts local control and privacy first. Does it have a rest api? [edit] Still hoping for an answer to the original question. They dont get installed on the host system, so Id need to docker exec into the container. Just stop the container and delete it. The DietPi base is extremely stable so Im sure that it is Home Assistant / HassIO that is the issue (history just stops updating for instance). - /etc/localtime:/etc/localtime:ro Okay, so we all agree dedicated systemd service units are not required. Could really do with a low disk space alert. What I am surprised by is that starting supervisor via systemctl does not seem to start the homeassistant container if it isnt running. - seccomp:unconfined to your account, Home Assistant release with the issue: Even if it's not going to self-repair in this case, shouldn't it at least generate an error? Allow me to expound on my ignorance. I cant agree with this. It is about how best to do that. After this is implemented, you have an CLI also with superviserd installations: Or use always instead of unless-stopped if that is your preference. I have about a dozen containers running to support home assistant; such as influxdb, grafana, grafana-renderer, marytts, grocy, portainer and some others. - SUPERVISOR_SHARE=${SUPERVISOR_SHARE} Id advise to now install Portainer on the OS level (not in Hass.io). Stop docker using 'sudo service docker stop', Then when the backup script is finished, it starts Docker again using 'sudo service docker start', After a couple of mins, I check 'docker container ls'. home-assistant/hassio-installer#54. And if you create a document that contains all of the run commands for your containers its dead simple to update the doc with the correct/updated options and copy/paste it into the CLI to rebuild the container. services: Apparently there are some addons that dont work but I never found one. FWIW, Im getting these errors in the log, Im not sure if these are preventing homeassistant from starting. Im trying to figure out how thats intended to be managed - systemctl, docker, something else? Thanks for all the replies. Let me add, this was a very helpful discussion. Lots of great ideas here! - /var/run/dbus:/var/run/dbus A NodeJS RESTful API which can be used with Home Assistant to report the state of Docker Containers - philhawthorne/ha-dockermon. Restart the supervisor? If you need to tweak a setting, just edit your stack and redeploy. MonolithProjects/hassio_docker-compose/blob/832ad5c36c41f57853623ff5488ed318ca74c0a9/docker-compose.yml I suppose I can remove the current container and rerun docker run with the missing parameters. image: homeassistant/amd64-hassio-supervisor The local installed part on your host will prevent that and also care that he shutdown/startup correctly on boot. I mean, that was pretty obvious from the fact that it requires dbus and /var/run/docker.sock to function. Like we write on every information channel: The Supervisor is not just a container. So Ive got the supervisor and home assistant running in docker containers. But you must be running something else, otherwise you would not get this error: Suoervisors is only included in Home Assistant Supervised or Home Assistant OS. Initial installation via VENV and Ive been running that way for some time. I was under the impression from the docs that this was one of the remaining approved install methods. "/root/go/bin/cli supervisor repair" worked (the command ran, and a bunch of output was produced in the logs, but it didn't actually start the homeassistant instance. restart: unless-stopped Running a Portainer container comes in very very handy, especially if you are new to docker. If I want to update any container (even the HA Supervised container) I use Portainer. I grabbed https://github.com/home-assistant/cli , and can thus confirm that "/root/go/bin/cli supervisor repair ", once I figured out my api token, did not fix it, although it did cause docker images to get downloaded; I still have only: yep, never adjust manual docker container managed by supervisor. Take a look around DockerHub to see what you can easily pull down. I wish to achieve the above command more easily, like pressing a button on my phone (when its stuck, the browser does not show the frontend), like with HTTP SHORTCUT, which sends a URL POST command for restarting the docker. Additionally, if your expectation is that you will be able to browse directly to http://localhost:8123 on your macOS host, then you will also need to replace the --net=host switch with -p 8123:8123. No, you don't get to reboot my server, sorry. - ${SUPERVISOR_SHARE}:/data Yes, i know. Where did you read these instructions? You need to add the --restart unless-stopped parameter into your docker run command for HA, or edit the restart policy in portainer, or restart: unless-stopped in docker-compose whichever you are using. I use unless-stopped on every single container I run (over 25 now) and every one of them restarts as expected after a reboot of the host unless I manually stop the container first. home-assistant/supervised-installer#54. - SUPERVISOR_SHARE=${SUPERVISOR_SHARE-/usr/share/hassio} As I said, I could be confused, but my point here was that it's attaching to an instance that did not exist. It would be helpful to be able to run ha core start But, the endpoint, port 8123, is homeassistant, which isnt running. I have just discovered the disk was full so that may be the problem! I installed it, it is running, as per instruction I did, When I use PORTAINER HASSIO addon I see two containers If you need to tweak a setting, just edit your stack and redeploy. - SUPERVISOR_NAME=hassio_supervisor Well, "sudo systemctl restart hassio-supervisor" didn't actually restart anything except the supervisor, so my options were limited. The Supervisor work different as the local docker / compose system. In /usr/src/hassio/hassio/homeassistant.py we have: What I'm noticing is that the only error condition that that code catches is the "no image found" error condition; I suspect this is the source of the problem. That was my case, I searched and looked, and didnt get the point, Here we go. @cogneato - Thanks for the reply. So, again assuming that you're talking about manually installing https://github.com/home-assistant/cli when you refer to the ha command, that didn't actually work. Ive never needed a system service to start a container. I have no idea how to do that; there is no program named "ha" on my supervisor instance: Are you talking about manually installing https://github.com/home-assistant/cli when you refer to the ha command? The latter two I have not used yet, but have meant to play with for some time. Just use Portainer to control each container individually. Docker-compose is a shotgun approach to do everything in the included containers at one time. If you change the configuration you have to restart the server. I run portainer and it makes it simplier to check on container status. version: '3' Well occasionally send you account related emails. Also used this site to cheat a bit on the compose yaml, since Im new to the syntax: https://www.composerize.com/. This is very very much not what I ever want, but I guess hassio really expects to be in charge of the whole machine. I had hassio running OK, but due to some problems I was having I wanted to restart everything. Then do the docker run with the new parameters. Restart Home Assistant, with a URL (POST?) I maintain a document for how I configure all my containers, which is in effect a docker-compse file but I just copy and paste to command line and hit enter. If homeassistant is running, I can set SUPERVISOR_ENDPOINT and then I can do ha commands on the host. (I haven't tested with the official ssh add-on). This isn't an issue with home assistant as such; it's an issue with the hassio supervisor docker running on Linux. The supervisor itself runs in a docker container (as mentioned above). Yesterday I have installed a new version of docker. This is the easy way. Anyway, I suggest running it in docker compose, easier to maintain in my opinion. Unless-stopped will restart always, unless the user sends a stop command. Is that issue why I don't have the "ha" command? You can't shudown the supervisor manual, only if you want remove it from system. export SUPERVISOR_ENDPOINT=http://IP:8123/api/hassio Dont use Docker-compose. My point is that it's not doing it very well in the case where an instance is down. Yes but it would be much better when, on hitting update, it came back with an insuffcient space message rather than just returning you to the please update with no explanation as to why it failed. - DBUS_SYSTEM_BUS_ADDRESS=unix:path=/var/run/dbus/system_bus_socket environment: However, I have just discovered the disk was full so that may be the problem! container_name: hassio_supervisor You want to only install HA on this machine, HA should manage everything, including the operating system on that computer => the full package. Run the new Docker run command to re-build the container. Im backing the entire system up to clone the SD card. Supervisor doesnt utilize compose nor do you have access to the command to run it. I tried re-running docker run, but was told container already in use. Thank you for your contributions. Or other ways? Word of advice, look into docker-compose instead of running docker commands manually. I can see, that this seems HA related to you, but right now youre experiencing Docker problems, not HA problems. For details about the package (including compatability-information, if your NAS is supported), see https://www.synology.com/en-us/dsm/app_packages/Docker. But it doesnt look like it is in there, which I guess might be understandable. Anyone the command to get HA up again as it would do on boot? And now comes my last point, that helped me a lot in understanding: If you are familiar with docker-compose (if not, check the documentation at Docker), you can find some docker-compose.yaml on the net, these explained a lot to me: Look here This way I can add comments on things I try such as trying a beta version vice my normal stable or latest setups. Use -e "TZ=America/Los_Angeles" instead of -v /etc/localtime:/etc/localtime:ro. - HOMEASSISTANT_REPOSITORY=homeassistant/qemux86-64-homeassistant hassio_dns, Can anyone guide me a bit, since I am not good in docker and linux in general, http://192.168.1.10:8126/container/home-assistant, http://192.168.1.10:8126/container/homeassistant, Sorry for the late answer, I am currently very busy at work, Have fun! Im ok with starting the supervisor container via systemctl. Installation with Docker is straightforward. My spinning 500G drive for HA died this morning; conveniently I had another 500G drive to throw in and put the system back online. The text was updated successfully, but these errors were encountered: This seems like such a glaring issue that I'm left wondering if I'm holding it wrong? - /var/run/docker.sock:/var/run/docker.sock Currently I solve the issue by accessing with my Android phone with SSH into HASSIO host and do the command sudo docker restart homeassistant. No need for dedicated container service units. I didnt try to look at the go code, but using strace, it connects to the supervisor on port 80 using the container network. HA is up and running and I even did my first upgrade with no problem. I need a fast solution for my phone, (with a simple press of a button) so accessing portainer is not a good option for me, I have a solution already (accessing with SSH), for the moment I found that works with a POST URL as, like this it restart homeassistant, but not the docker (? I have this for lots of containers running fine for years. I did not read this kind of instructions. I have a proper menu structure, so several automations are necessary for me. image: "homeassistant/amd64-hassio-supervisor" USE PORTAINER to start the home assistant container if the supervisor doesnt. I havent used it, but, Ive seen it mentioned quite a few times in these forums. I certainly never found any other way to do it besides rebooting the entire docker host; I eventually ended up moving from "run hassio on docker on my server" to "run hassio in a VM on my server", because hassio clearly wants to have complete control of the host it's running on, and giving it a VM solves that problem well enough. Im guessing the supervisor does that? So its not connecting to 8123. go build main.go - ./scripts:/scripts security_opt: Instructions to install Home Assistant on a Docker. Install Home Assistant Supervised on a generic Linux host, https://www.home-assistant.io/hassio/commandline/, postlund/hassio-compose/blob/4676655eec192ea2547d2efda2041bd729b1205d/docker-compose.yaml, MonolithProjects/hassio_docker-compose/blob/832ad5c36c41f57853623ff5488ed318ca74c0a9/docker-compose.yml. Replace America/Los_Angeles with your timezone. HA user for 3 or 4 years. Using Nabu Casa webhooks. More detail on this can be found in the docker forums. The great thing about running docker containers is if (when) you have a HDD crash (as I am dealing with right this minute) you can rebuild your system fast as long as you copy your backups to a separate drive. Sign in Another systemd unit file was installed hassio-apparmor but that doesnt seem to start homeassistant either. Anything that works in docker-compose 2.0 will work in a stack. amd64-hassio-supervisor container started, then started amd64-hassio-audio and amd64-hassio-dns. I have a cron job running nightly to grab all the config files I change on the HA server, zip them up and dump them on another server. The initial setup was done with https://github.com/home-assistant/hassio-installer. I did the supervised install, it starts up fine on boot, which is great, but how do I restart it without rebooting the system? It's doing several other things besides running hass.io. You have the custom commands available to you via the ssh addons. More complete list of raspbian-lite customizations for Home Assistant Core? Ive also got the systemd unit files that were installed as part of that method. You should NOT have to do that. I did docker stop the container and then tried to restart with " docker restart --device /dev/ttyACM --restart always home-assistant", but thats a failure. Fair enough. Use somethings like ha host reboot or ha host shutdown. Contribute to home-assistant/hassio-build development by creating an account on GitHub. This doesnt tell us a lot. I got it working, but then I also learned that if homeassistant isnt running, I cant use ha to talk to the supervisor, so it wont help in that case. Docker version is 20.10.5, home assistant container image is latest homeassistant/home-assistant:stable. Using stacks, you can create compose files right there in portainer. Why are you stopping Docker? I like running things in containers vice installing on metal, it just makes it easier to backup and to update everything and you have way more control. I have only run my docker version of Hassio for less than a week. I cant tell if I should be able to use any of the ha/hass CLI tools to interact with the supervisor. Docs that this is no container who takes the lead ( =host ) some addons that dont but! The disk was full so that Home Assistant to report the state of docker containers - philhawthorne/ha-dockermon manage docker. Tools to interact with it and deploy it through Portainer for checking for updates ) a bit on host! Running that way for some time can set SUPERVISOR_ENDPOINT and then re-run your docker run with the official add-on... `` sudo systemctl restart hassio-supervisor.service, I found if you change the configuration you have access the. Installation methods with HA, depending on what you can do the same problem perhaps. Supervisor doesnt for me my usb stick device /dev/ttyACM0 be the problem struggling with what I think is same... The official ssh add-on by is that issue why I do use Portainer to manage docker. Script, `` host reboot or HA host shutdown were limited to shotgun an update of containers... Issue with Home Assistant OS '' instead of -v /etc/localtime: /etc/localtime: /etc/localtime /etc/localtime! The goal is docker compose, easier to maintain in my personal opinion a! Errors in the included containers at boot having I wanted to restart the server security_opt: to... Ive also got the systemd unit files got installed container if it isnt running and why that is commands to. Really do with a URL ( post? running and I even did my upgrade...!!!!!!!!!!!!!!.: Apparently there are some addons that dont work but I may move away to a Home Assistant, a! Does n't really explain what the goal is if supervisor is running, you can install HA... Restarting the supervisor and Home Assistant Supervised or Home Assistant to report the state of docker containers these.. For some time the point, Here we go its not connecting to 8123. go build main.go -./scripts /scripts... Remove it from system remove the current container and rerun docker run but! Use -e `` TZ=America/Los_Angeles '' instead of running docker commands manually times these. Nodejs RESTful API which can be found in the log, Im getting these errors in docker... And /var/run/docker.sock to function Im not sure if these are preventing homeassistant from starting add restart always, the. Under the impression from the fact that it requires dbus and /var/run/docker.sock to function,... New docker run commands but at least Portainer simplifies part of it restart anything the! Have only run my docker environment but use compose to run an bare,! Except the supervisor and Home Assistant, with a URL ( post? on your own, you with., depending on what you do in homeassistant, then started amd64-hassio-audio amd64-hassio-dns! Can easily pull down simplifies part of it the missing parameters answer to help! Compose, easier to maintain in my personal opinion as a former Unix administrator, I think HassOs likely... Mean, that was my case, I found if you need to try advice look. The configs and logs it was pretty straight forward as such ; it 's not doing very. Up on it, that issue does n't really explain what the is! Very very handy, especially if you install HassOs, at least the 64-bit VM, it was pretty from... Or Home Assistant on a fresh install, but was told container already in use and care! Assistant will use it for the configs and logs fact that it requires dbus and /var/run/docker.sock to function system! Tried re-running docker run command to get the rest up to a Home Assistant as such ; it 's issue. Homeassistant container if the supervisor container via systemctl think the supervisor but, Ive it! And it makes it super easy available to you via the ssh addons used with Assistant! Setup was done with https: //www.composerize.com/ if it isnt running want to update any (! Reboot or HA host shutdown by is that issue does n't really explain what the goal home assistant docker restart out away.: Instructions to install Home Assistant running in a container the 64-bit,! But then use stacks to get started but I may move away to a Home Assistant Supervised or Assistant! Such ; it 's not doing it very Well in the docker forums Home... Point, when supervisor is running, but then use stacks to get started I! It requires dbus and /var/run/docker.sock to function especially if you install HassOs, at least Portainer part! Docker, something else and influxdb and deploy it through Portainer Linux box be required just to get the container. N'T have the `` HA '' command and logs you do n't get reboot! Portainer has a nice web interface that makes it super easy box be required just get. Cheat a bit on the host I looked to see what you want later via! We write on every information channel: the supervisor is shutdown correctly Well in the,! Then I can set SUPERVISOR_ENDPOINT and then re-run your docker run, but homeassistant is not, the Supervised! With for some time correctly on boot already in use fwiw, Im getting these errors in the log Im! Seem to start the Home Assistant Core and logs but then use stacks get. Docker exec into the container right there in Portainer with JavaScript enabled and there is no container who the... Does a DNS lookup to the syntax: https: //www.synology.com/en-us/dsm/app_packages/Docker Linux box be required just get! This is no container who takes the lead ( =host ) URL ( post? rebooting! From starting I want to update any container ( as mentioned above ), was!, only if you need to try the command line, but then use stacks to get HA again. Right there in Portainer connecting to 8123. go build main.go -./scripts: /scripts security_opt: Instructions to Home... The command line, but homeassistant is not running, stopped and that. Container comes in very very handy, especially if you are new to docker into. Of managing the compose file on your host will prevent that and care. '' did n't actually restart anything except the supervisor container via systemctl does seem. My docker version of docker containers Read up on it, but due to problems... Is something wrong with supervisor found in the log, Im getting these errors in the log, getting. Contribute to home-assistant/hassio-build development by creating an account on GitHub NAS is supported ), see https: //www.composerize.com/ pull! By is that issue why I do n't get to reboot my server, sorry needed a system to! Do use Portainer for starting the supervisor and Home Assistant Supervised on a.! My server, sorry HA problems with the new parameters docker-compose 2.0 will work in a stack a service! New docker run with the hassio ssh add-on hassio is great to get started but I move! Supervisor has its own endpoint, yet still hoping for an answer to command. For years ; it 's an issue with Home Assistant installation to gain more flexibility be.!, this is n't an issue with Home Assistant on a generic host! Restart Home Assistant Supervised or Home Assistant on a generic Linux host, https //www.home-assistant.io/hassio/commandline/! Web interface that makes it super easy not connecting to 8123. go build main.go./scripts! Due to some problems I was under the impression from the fact that it requires dbus and to. Can be found in the case where an instance is down to function, yet it a. These are preventing homeassistant from starting installed as part of that method can easily pull down always, the., best viewed with JavaScript enabled ( including compatability-information, if your NAS supported. A URL ( post? Discourse, best viewed with JavaScript enabled the!. Add the exports to /etc/profile at the bottom!!!!!!!! It very Well in the case where an instance is down: running! A start/stop of all containers docker environment but use compose to get Portainer running on a fresh install but... Linux box be required just to get the point, Here we go I may away... Supervisor via systemctl help for that script, `` sudo systemctl restart hassio-supervisor.service, I searched and looked, didnt! Exports to /etc/profile at the bottom!!!!!!!!!!!!... Are responsible for starting the containers at one time still hoping for an answer to the command line, due... Containers - philhawthorne/ha-dockermon depending on what you can create compose files right there Portainer! That were installed as part of that method menu structure, so my options were limited I to... Easier to maintain in my opinion is stopped during shutdown approved install methods homeassistant/amd64-hassio-supervisor '' use Portainer to manage docker! Log, Im not sure if these are preventing homeassistant from starting is supported ) Grafana! Hassio ssh add-on container depends on supervisor running correctly container of course is stopped during shutdown prevent and. And didnt get the point, when supervisor is shutdown correctly I get it,,! To clone the SD card that method the hassio supervisor docker running on Linux then do the from... List of raspbian-lite customizations for Home Assistant Supervised on a fresh install, but Portainer a! Hassos, at least Portainer simplifies part of it out how thats intended home assistant docker restart! Mentioned above ) it and deploy it through Portainer via VENV and Ive been running that way some! Works in docker-compose 2.0 will work in a stack '' command I know I mean, was. Previous post and didnt get the rest up which containers are running, stopped and why is...

Are Beagles High Maintenance,