40b4d5ca2e
* Start ha-cli on tty1 instead of a getty Instead of starting a getty start the ha-cli directly. This will show the banner right on startup with the important information such as IP address of the instance or the URL to reach it. * Use default shell as root shell instead of HA CLI Instead of using the ha-cli.sh script as login shell use the regular shell. Amongst other things, this allows to run VS Code devcontainers remotely via SSH or using scp. The HA CLI is still available using the `ha` command.
26 lines
622 B
Bash
Executable File
26 lines
622 B
Bash
Executable File
#!/bin/sh
|
|
# ==============================================================================
|
|
# Run logging cli
|
|
# ==============================================================================
|
|
|
|
echo "Waiting for the Home Assistant CLI to be ready..."
|
|
|
|
i=0
|
|
while [ ! "$(docker ps -q -f name=hassio_cli)" ]; do
|
|
sleep 1
|
|
i=$((i+1))
|
|
if [ $i = 60 ]; then
|
|
echo "[WARN] Home Assistant CLI not starting! Jump into emergency console..."
|
|
exec /bin/ash -l
|
|
fi
|
|
done
|
|
|
|
docker container exec \
|
|
-ti hassio_cli \
|
|
/usr/bin/cli.sh
|
|
|
|
# Jump to root login shell
|
|
if [ $? -eq 10 ]; then
|
|
exec /bin/ash -l
|
|
fi
|