Skip to content
Installer for a generic Linux system
Branch: master
Clone or download
unlucio and pvizeli Warn the user about NOT deleting containers (#12)
* Warn the user about NOT deleting containers

As the `supervisor` does not support creating the homeassistant container if accidentally deleted, let's warn the users before it's too late and perhaps give a bare minimum of possible ways to recover.

* Update README.md
Latest commit 1c93a06 May 23, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
files Fix lint Apr 24, 2019
LICENSE [skip ci] add licences Apr 25, 2019
README.md Warn the user about NOT deleting containers (#12) May 23, 2019
azure-pipelines.yml Fix lint Apr 24, 2019
hassio_install.sh Fix broken links (#2) Apr 24, 2019

README.md

Build Status

Install Hass.io

Beside the usage of the images it's also possible to run Hass.io on a generic system without flashing an image.

Requirements

docker-ce
bash
jq
curl
avahi-daemon
dbus

Optional

apparmor-utils
network-manager

Run

Run as root (sudo su):

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | bash -s

Command line arguments

argument default description
-m | --machine On a special platform they need set a machine type use
-d | --data-share /usr/share/hassio data folder for hass.io installation

you can set these parameters by appending -- <parameter> <value> like:

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | bash -s -- -m MY_MACHINE

Supported Machine types

  • intel-nuc
  • odroid-c2
  • odroid-xu
  • orangepi-prime
  • qemuarm
  • qemuarm-64
  • qemux86
  • qemux86-64
  • raspberrypi
  • raspberrypi2
  • raspberrypi3
  • raspberrypi3-64
  • tinker

!!!WARNING!!! DO NOT DELETE CREATED CONTAINERS

This installer will create the base homeassistant container for you, but if you delete if (docker rm or docker prune) the supervisor will not be able to re-create it for you. Hass.io is a Eco System and Container Orchastrator they don't support manual adjustments.

If you wish to still safelly use docker containers prune you might want to add the --filter flag to your command.

Example:

$ docker container prune --filter label!=homeassistant

or, for a greater peace of mind, you can add the following config to your ~/.docker/config.json:

{
  "pruneFilters": ["label!=homeassistant", "label!=hassio_supervisor", "label!=addon*"]
}
You can’t perform that action at this time.