![]() When starting Supervisor often the terminal messed up. From investigation it seemed that dockerd messes with the terminal somehow, carriage returns (\r) seem not to function properly. Resetting the terminal fixes this. While add it, also use the Docker daemon PID from the pid file. This is a different PID than before, since this is the actual daemon PID and not the PID of the sudo process that starts the daemon. This should not really make a difference, since killing the sudo process seemed to have passed the signal along to the daemon, but it is cleaner to use the actual daemon PID. |
||
---|---|---|
.github | ||
addons | ||
common | ||
supervisor | ||
.devcontainer.json | ||
LICENSE | ||
README.md |
README.md
devcontainer
This project contains custom devcontainers for use in our repositories.
Images
Image | Description | Dockerfile |
---|---|---|
ghcr.io/home-assistant/devcontainer:addons |
For Add-on development | ./addons/Dockerfile |
ghcr.io/home-assistant/devcontainer:supervisor |
For Supervisor development | ./supervisor/Dockerfile |
Versioned images are available with the custom devcontainer version prepended (e.g. 1-supervisor
). This loosly resembles what
upstream devcontainers are providing as well. The version is meant to be incremented when non-backwards compatible changes are
made. That allows existing devcontainer configuration to work while updating the devcontainers (e.g. when the Supervisor devcontainer
is updated to a new Python version).
Example files
Example files to use with Visual Studio Code
addon
Example files for the addons
devcontainer
- Example configuration (for
.devcontainer/devcontainer.json
) - Example tasks file (for
.vscode/tasks.json
)
Notes
addons
and supervisor
- Use the command
supervisor_run
to start Home Assistant inside the devcontainer, or run the task "Start Home Assistant" if you copied the tasks file. - Use
ha
to use the custom Home Assistant CLI (Needs the supervisor to be running).