Configuration.yml not loaded after hard reboot (docker)

Configuration
1

Hello,

I use home assistant through the official docker image. A few days ago my host sytem had a hard reboot after which homeassistant stopped working. Or rather, it works but it does not pick up my configuration files; the interface provides me with the default blank slate without fault so far.

docker-compose:

version: '3'


services:
  db:
    image: postgres:alpine
    restart: always
    volumes:
      - dbhassvol:/var/lib/postgresql/data

  hass:
    image: homeassistant/home-assistant:latest
    restart: always
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ${HOME}/projects/home-assistant:/config
    ports:
      - 8123:8123
    devices:
      - /dev/ttyUSB0:/dev/zwave:rwm
    depends_on:
      - db

volumes:
  dbhassvol:
    driver: local

I have not made any changes to the homeassistant configuration files in the interim.

As far as I can see, the configuration folder is (still) mapped correctly. When I console into the docker instance, I can see the configuration folder at /config. I do not understand what is going wrong here.

2

Delete then rebuild container.

What does log show?
Frontend loads OK?(do you get default page)

3

Prior to making this post, I did delete all containers, networks, etc, except the DB volume. To no avail. Front-end loads OK, it just shows me the introduction; ie. a fresh start.

Logs are fine, no errors.

$ docker-compose up
Creating network "homeassistant_internal" with the default driver
Creating homeassistant_db_1 ...
Creating homeassistant_db_1 ... done
Creating homeassistant_hass_1 ...
Creating homeassistant_hass_1 ... done
Attaching to homeassistant_db_1, homeassistant_hass_1
db_1    | 2018-02-23 09:57:24.938 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
db_1    | 2018-02-23 09:57:24.939 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db_1    | 2018-02-23 09:57:24.947 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1    | 2018-02-23 09:57:24.991 UTC [17] LOG:  database system was shut down at 2018-02-23 09:56:48 UTC
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_off>
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=turn_on>
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=toggle>
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=stop>
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=restart>
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=check_config>
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=homeassistant, service=reload_core_config>
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=persistent_notification, service=create>
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=persistent_notification, service=dismiss>
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.bootstrap] Home Assistant core initialized
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.loader] Loaded introduction from homeassistant.components.introduction
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.setup] Setting up introduction
hass_1  | 2018-02-23 09:57:28 INFO (MainThread) [homeassistant.components.introduction]
...

The introduction component is the first thing that’s loaded, even though I do not have it enabled in my configuration.yml. In other words, my configuration does not seem to be detected at all.

4

I guess if you ssh you can access this location?

5

It appears my config folder is not mapped correctly. I thought it was, but the container has just created the default files.

I’ll try to get the container to add the volume correctly. This is probably what’s causing the problem. I still don’t understand why, but I can probably fix this.

6

Could there be any issue with the docker image?

Whatever I do, the /config directory within the container seems to be overwritten with the default home-assistant starter files (see below). I have no clue what’s going on.

-rw-r--r-- 1 root root     2 Feb 26 21:54 automations.yaml
-rw-r--r-- 1 root root  1788 Feb 26 21:54 configuration.yaml
-rw-r--r-- 1 root root     0 Feb 26 21:54 customize.yaml
drwxr-xr-x 2 root root  4096 Feb 26 21:54 deps
-rw-r--r-- 1 root root     0 Feb 26 21:54 groups.yaml
-rw-r--r-- 1 root root  3968 Feb 26 21:58 home-assistant.log
-rw-r--r-- 1 root root 48128 Feb 26 22:00 home-assistant_v2.db
-rw-r--r-- 1 root root     0 Feb 26 21:54 scripts.yaml
-rw-r--r-- 1 root root   157 Feb 26 21:54 secrets.yaml
drwxr-xr-x 2 root root  4096 Feb 26 21:54 tts

For the record, I’m running Docker Toolbox on OSX.