kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Documentation
rodzic
27bda411c6
commit
649916f084
|
@ -40,6 +40,35 @@ This image is based on Home Assistant Core.
|
||||||
|
|
||||||
The Webui can be found at `http://your-ip:8123`. Follow the wizard to set up Home Assistant.
|
The Webui can be found at `http://your-ip:8123`. Follow the wizard to set up Home Assistant.
|
||||||
|
|
||||||
|
### Host vs. Bridge
|
||||||
|
|
||||||
|
Home Assistant can [discover][hb0] and automatically configure
|
||||||
|
[zeroconf][hb1]/[mDNS][hb2] and [UPnP][hb3] devices on your network. In
|
||||||
|
order for this to work you must create the container with `--net=host`.
|
||||||
|
|
||||||
|
[hb0]: https://www.home-assistant.io/integrations/discovery/#mdns-and-upnp
|
||||||
|
[hb1]: https://en.wikipedia.org/wiki/Zero-configuration_networking
|
||||||
|
[hb2]: https://en.wikipedia.org/wiki/Multicast_DNS
|
||||||
|
[hb3]: https://en.wikipedia.org/wiki/Universal_Plug_and_Play
|
||||||
|
|
||||||
|
### Accessing Bluetooth Device
|
||||||
|
|
||||||
|
In order to provide HA with access to the host's Bluetooth device, one needs to install BlueZ on the host, add the capabilities `NET_ADMIN` and `NET_RAW` to the container, and map dbus as shown in the below examples.
|
||||||
|
|
||||||
|
#### Docker Cli:
|
||||||
|
```bash
|
||||||
|
--cap-add=NET_ADMIN --cap-add=NET_RAW --device /var/run/dbus:/var/run/dbus:ro
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Docker Compose:
|
||||||
|
```yaml
|
||||||
|
cap_add:
|
||||||
|
- NET_ADMIN
|
||||||
|
- NET_RAW
|
||||||
|
devices:
|
||||||
|
- /var/run/dbus:/var/run/dbus:ro
|
||||||
|
```
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
|
||||||
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
|
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
|
||||||
|
@ -83,18 +112,6 @@ docker run -d \
|
||||||
lscr.io/linuxserver/homeassistant:latest
|
lscr.io/linuxserver/homeassistant:latest
|
||||||
```
|
```
|
||||||
|
|
||||||
#### Host vs. Bridge
|
|
||||||
|
|
||||||
Home Assistant can [discover][hb0] and automatically configure
|
|
||||||
[zeroconf][hb1]/[mDNS][hb2] and [UPnP][hb3] devices on your network. In
|
|
||||||
order for this to work you must create the container with `--net=host`.
|
|
||||||
|
|
||||||
[hb0]: https://www.home-assistant.io/integrations/discovery/#mdns-and-upnp
|
|
||||||
[hb1]: https://en.wikipedia.org/wiki/Zero-configuration_networking
|
|
||||||
[hb2]: https://en.wikipedia.org/wiki/Multicast_DNS
|
|
||||||
[hb3]: https://en.wikipedia.org/wiki/Universal_Plug_and_Play
|
|
||||||
|
|
||||||
|
|
||||||
## Parameters
|
## Parameters
|
||||||
|
|
||||||
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
|
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
|
||||||
|
@ -316,6 +333,7 @@ Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64
|
||||||
|
|
||||||
## Versions
|
## Versions
|
||||||
|
|
||||||
|
* **18.12.23:** - Add Bluetooth instructions to readme.
|
||||||
* **05.07.23:** - Deprecate armhf. As announced [here](https://www.linuxserver.io/blog/a-farewell-to-arm-hf)
|
* **05.07.23:** - Deprecate armhf. As announced [here](https://www.linuxserver.io/blog/a-farewell-to-arm-hf)
|
||||||
* **21.06.23:** - Pin pycups version.
|
* **21.06.23:** - Pin pycups version.
|
||||||
* **14.06.23:** - Create secondary venv in `/config` for pip installs.
|
* **14.06.23:** - Create secondary venv in `/config` for pip installs.
|
||||||
|
|
Ładowanie…
Reference in New Issue