Skip to content

Latest commit

 

History

History
 
 

homeassistant-base

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

homeassistant-base

CONTAINERS IMAGES RUN BUILD

CONTAINERS
homeassistant-base
   Requires L4T ['>=34.1.0']
   Dependencies build-essential
   Dependants homeassistant-core:2024.4.2 homeassistant-core:latest wyoming-assist-microphone:latest wyoming-openwakeword:latest wyoming-piper:master wyoming-whisper:latest
   Dockerfile Dockerfile
   Notes The homeassistant base ubuntu image with pre-installed dependencies based on https://github.com/home-assistant/docker-base/blob/master/ubuntu/Dockerfile
RUN CONTAINER

To start the container, you can use jetson-containers run and autotag, or manually put together a docker run command:

# automatically pull or build a compatible container image
jetson-containers run $(autotag homeassistant-base)

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host homeassistant-base:35.2.1

jetson-containers run forwards arguments to docker run with some defaults added (like --runtime nvidia, mounts a /data cache, and detects devices)
autotag finds a container image that's compatible with your version of JetPack/L4T - either locally, pulled from a registry, or by building it.

To mount your own directories into the container, use the -v or --volume flags:

jetson-containers run -v /path/on/host:/path/in/container $(autotag homeassistant-base)

To launch the container running a command, as opposed to an interactive shell:

jetson-containers run $(autotag homeassistant-base) my_app --abc xyz

You can pass any options to it that you would to docker run, and it'll print out the full command that it constructs before executing it.

BUILD CONTAINER

If you use autotag as shown above, it'll ask to build the container for you if needed. To manually build it, first do the system setup, then run:

jetson-containers build homeassistant-base

The dependencies from above will be built into the container, and it'll be tested during. Run it with --help for build options.