Thank you for your reply. I visited that link, but far from making it clear, it creates more confusion for me. But aside, this does not help me anyway.
To expand insight into my problem…
My /etc/hassio.json is:
What I am seeking to do is symlink the config dir, which is (using the data in the above config):-
…which is where configuration.yaml and other yam config files are held.
So, my config dir in /home/ha/HOMEASSISTANT/HASSIO/DATA_SHARE looks like this
lrwxrwxrwx 1 ha ha 5 Dec 2 21:21 homeassistant -> /home/ha/test1
And i would like to change the link to point to different test dirs, depending on what I am testing.
lrwxrwxrwx 1 ha ha 5 Dec 2 21:21 homeassistant -> /home/ha/test2
lrwxrwxrwx 1 ha ha 5 Dec 2 21:21 homeassistant -> /home/ha/test3
This allows (or rather it would do if working) my HA core to run and at each startup pickup a config depending on where the link points to. But it doesn’t work. The homeassistant link is not being followed. The homeassistant dir must be a true directory - not a symlink - otherwise core will create a default config.
Now, as am running hassio, the file structure is different with different volumes used, compared to homeassistant core.
In hassio the usual /usr/share/homeassistant can be remapped using the data key/value pair, as indeed I have done in myhassio.json - as above.
Homeassistant core does things differently. It looks for /config which can be mapped as a volume name passed into the docker command (-v) or as a volumes entry in a docker-compose.yaml file. So all that I need to do here is simply pass a different host directory with the -v flag, I do not even need to use symlinks, as in one of:-
docker run -it -v $(readlink -f /home/ha/test1/):/config/ ...
docker run -it -v $(readlink -f /home/ha/test2/):/config/ ...
docker run -it -v $(readlink -f /home/ha/test3/):/config/ ...
I have only just moved from a simple homeassistant core installation, to the more complex hassio docker (yes “unsupported” I know). I am unsure how to achieve what I want using hassio docker and I am unsure how the container containing the core is started and how and where - I guess if I knew I could change it perhaps to pass a -v argument in ?
Hope this explains. It’s almost like I want to be able to pass a config key/pair using /etc/hassio.json - but I cannot find any docs on what config options can go into /etc/hassio.json.