My HASSIO container disappeared .... help!

This morning my HASSIO on NUC disappeared, not sure what happened.

I was used to restart it logging SSH on my NUC and then

io@ubuntu:~$ docker restart homeassistant
Error response from daemon: No such container: homeassistant

seems no container are present

io@ubuntu:~$ docker container list
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

And since I had my dropbox always full, yesterday I deleted all my backups, great (still hope for an addon that saves ONLY last 2 backups and not all of them)

How to access /backup of the NUC? I can SSH in “normal” NUC not inside HASSIO, it gives connection refused

docker container list -a

What is the output ?

Nothing.

I solved by reinstalled docker cè, all dependencies needed, again HASSIO, and puff all was working again, all files still there.

Strange

@Klagio I believe there is a dropbox addon that supports retaining only X number of backups. It’s based upon number of days. https://github.com/danielwelch/hassio-dropbox-sync. Since you are using dropbox to do your back ups that might help you with the problem of having to many back ups. I’m unsure if it deletes from dropbox but I know it removes them from your hassio instance.

this keeps a number of X (customizable) of backup on the server and uploads them to dropbox DELETING the other backups from the server.

What I wish for is keeping all the backups on the server and upload to dropbox only 2. I have space problem in dropbox, not the server

Ah sorry I misunderstood where you wanted to delete from.

A simple script on your server will realise that. It is a server backup problem, not a ha problem.

Again I have sdame problem, but this time I can’t solve it … I am stuck

root@ubuntu:~# docker restart homeassistant
Error response from daemon: No such container: homeassistant
root@ubuntu:~# docker container list -a
CONTAINER ID        IMAGE                                   COMMAND               CREATED             STATUS              PORTS               NAMES
703ca674677c        homeassistant/amd64-hassio-supervisor   "python3 -m hassio"   2 seconds ago       Created                                 hassio_supervisor
root@ubuntu:~#

I did this too, but is it not installing??

root@ubuntu:~# curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install" | bash -s
[Info] Install supervisor Docker container
[Info] Install supervisor startup scripts
[Info] Install AppArmor scripts
[Info] Run Hass.io
root@ubuntu:~#

Are you guys running docker-ce or docker.io?

I have seen people have problems with docker.io, which is why everyone says to run docker-ce

1 Like

I red that, so I spoecifically installed docker-ce

Weird, never had this problems, below the output of a couple of commands. But have no idea how docker works

root@ubuntu:/usr/local/bin# docker ps
CONTAINER ID        IMAGE                 COMMAND             CREATED             STATUS              PORTS                    NAMES
f0ba7bb67662        portainer/portainer   "/portainer"        5 minutes ago       Up 5 minutes        0.0.0.0:9000->9000/tcp   goofy_clarke
root@ubuntu:/usr/local/bin# docker ps -l
CONTAINER ID        IMAGE                                   COMMAND               CREATED             STATUS              PORTS               NAMES
38f47f1555fa        homeassistant/amd64-hassio-supervisor   "python3 -m hassio"   6 seconds ago       Created                                 hassio_supervisor
root@ubuntu:/usr/local/bin#

hassio is using a systemd service to run the supervisor. check journalctl -xe

Now I uninstalled docker-ce, and reinstalled it, it seems to work (hope I did not loose all myu configuration)

root@ubuntu:~# docker ps
CONTAINER ID        IMAGE                                    COMMAND               CREATED              S                               TATUS              PORTS               NAMES
55ed21c549a5        homeassistant/qemux86-64-homeassistant   "/usr/bin/entry.sh"   57 seconds ago       U                               p 56 seconds                           homeassistant
4c1113b500d1        homeassistant/amd64-hassio-supervisor    "python3 -m hassio"   About a minute ago   U                               p About a minute                       hassio_supervisor
root@ubuntu:~# docker restart homeassistant
homeassistant
root@ubuntu:~# journalctl -xe
Jan 15 14:59:40 ubuntu upowerd[3590]: (upowerd:3590): UPower-Linux-WARNING **: treating change event as a
Jan 15 14:59:40 ubuntu upowerd[3590]: (upowerd:3590): UPower-Linux-WARNING **: treating change event as a
Jan 15 14:59:40 ubuntu upowerd[3590]: (upowerd:3590): UPower-Linux-WARNING **: treating change event as a
Jan 15 14:59:40 ubuntu systemd-udevd[29625]: Process '/sbin/crda' failed with exit code 234.
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3558] device changed (path: /sys/devices
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3796] device changed (path: /sys/devices
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3848] device changed (path: /sys/devices
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3850] device changed (path: /sys/devices
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3894] device changed (path: /sys/devices
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3904] device changed (path: /sys/devices
Jan 15 14:59:40 ubuntu upowerd[3590]: (upowerd:3590): UPower-Linux-WARNING **: treating change event as a
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3938] device changed (path: /sys/devices
Jan 15 14:59:42 ubuntu ModemManager[1274]: <info>  Couldn't check support for device at '/sys/devices/pci
Jan 15 14:59:42 ubuntu ModemManager[1274]: <info>  Couldn't check support for device at '/sys/devices/pci
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.009337760+01:00" level=debug msg="
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.010407127+01:00" level=debug msg="
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.128398430+01:00" level=warning msg
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.133270999+01:00" level=debug msg="
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.134977025+01:00" level=debug msg="
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.136184560+01:00" level=debug msg="
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.136225300+01:00" level=debug msg=V
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.136883391+01:00" level=debug msg="
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.137749718+01:00" level=debug msg="
Jan 15 14:59:59 ubuntu ModemManager[1274]: <info>  Creating modem with plugin 'Generic' and '1' ports
Jan 15 14:59:59 ubuntu ModemManager[1274]: <warn>  Could not grab port (tty/ttyACM0): 'Cannot add port 't
Jan 15 14:59:59 ubuntu ModemManager[1274]: <warn>  Couldn't create modem for device at '/sys/devices/pci0
lines 1302-1327/1327 (END)
Jan 15 14:59:40 ubuntu upowerd[3590]: (upowerd:3590): UPower-Linux-WARNING **: treating change event as add on /sys/devices/virtual/inpu
Jan 15 14:59:40 ubuntu upowerd[3590]: (upowerd:3590): UPower-Linux-WARNING **: treating change event as add on /sys/devices/virtual/inpu
Jan 15 14:59:40 ubuntu upowerd[3590]: (upowerd:3590): UPower-Linux-WARNING **: treating change event as add on /sys/devices/pnp0/00:01/r
Jan 15 14:59:40 ubuntu systemd-udevd[29625]: Process '/sbin/crda' failed with exit code 234.
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3558] device changed (path: /sys/devices/virtual/net/hassio, iface: has
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3796] device changed (path: /sys/devices/virtual/net/veth9beea11, iface
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3848] device changed (path: /sys/devices/virtual/net/tun0, iface: tun0)
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3850] device changed (path: /sys/devices/virtual/net/lo, iface: lo)
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3894] device changed (path: /sys/devices/virtual/net/veth7610612, iface
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3904] device changed (path: /sys/devices/virtual/net/vethf25e2af, iface
Jan 15 14:59:40 ubuntu upowerd[3590]: (upowerd:3590): UPower-Linux-WARNING **: treating change event as add on /sys/devices/virtual/inpu
Jan 15 14:59:40 ubuntu NetworkManager[1327]: <info>  [1547560780.3938] device changed (path: /sys/devices/virtual/net/docker0, iface: do
Jan 15 14:59:42 ubuntu ModemManager[1274]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:19.0': not supp
Jan 15 14:59:42 ubuntu ModemManager[1274]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.3/0000:02:00
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.009337760+01:00" level=debug msg="Calling GET /_ping"
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.010407127+01:00" level=debug msg="Calling GET /v1.24/info"
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.128398430+01:00" level=warning msg="failed to retrieve docker-run
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.133270999+01:00" level=debug msg="Calling GET /v1.24/containers/j
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.134977025+01:00" level=debug msg="Calling GET /v1.24/images/json"
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.136184560+01:00" level=debug msg="Calling GET /v1.24/volumes"
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.136225300+01:00" level=debug msg=VolumeStore.Find ByType=service.
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.136883391+01:00" level=debug msg="Calling GET /v1.24/networks"
Jan 15 14:59:53 ubuntu docker.dockerd[1526]: time="2019-01-15T14:59:53.137749718+01:00" level=debug msg="Calling GET /v1.24/version"
Jan 15 14:59:59 ubuntu ModemManager[1274]: <info>  Creating modem with plugin 'Generic' and '1' ports
Jan 15 14:59:59 ubuntu ModemManager[1274]: <warn>  Could not grab port (tty/ttyACM0): 'Cannot add port 'tty/ttyACM0', unhandled serial t
Jan 15 14:59:59 ubuntu ModemManager[1274]: <warn>  Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3':
lines 1302-1327/1327 (END)

Your HA configuration should not live INSIDE the docker containers. It lives on the host. It is persistent data

Piufff! great, and you know where is it?

If you read the script you ran…

https://github.com/home-assistant/hassio-build/blob/master/install/hassio_install

DATA_SHARE=/usr/share/hassio

1 Like

Well thanks thats a relief.

Anyway, HASSIO is not starting, since now I do not have SSH access to it, I also don’t know what to do. In the past I did port 22 for SSH to the HOST and port 23 to access SSH to HASSIO, now port 23 is not giving access