configpolicy/main.yml at 84313601efdf9cfc838626f9b7572ad7f893cfde - configpolicy - Gitea: Git with a cup of tea

dustin/configpolicy

Files

Dustin C. Hatch b99c7aa27d roles/homeassistant: Install in a virtualenv

Because the Home Assistant user's home directory is on `/var`, Python
packages installed in the "user site" do not get the correct SELinux
labels and thus run in the wrong domain.  This causes a lot of AVC
denials and other issues that prevent Home Assistant from working
correctly.

To resolve this issue, Home Assistant is now installed in a virtual
environment at `/usr/local/homeassistant`.  This directory is still
owned by the Home Assistant user, allowing Home Assistant to manage
packages installed there.  Since it is rooted under `/usr`, files are
labelled correctly and processes launched from executables there will
run in the correct domain.

2020-07-04 14:25:16 -05:00

3 lines

48 B

YAML

Raw Blame History

	`homeassistant_common_system_deps:`
	`- python3-pip`