@frostwork 1. I'm already watching that thread. 2. I would have uses pyenv for intalling another python. 3. I think I understand the problem now.
Search Criteria
Package Details: homeassistant-supervised 2.0.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/homeassistant-supervised.git (read-only, click to copy) |
---|---|
Package Base: | homeassistant-supervised |
Description: | Home Assistant Supervised |
Upstream URL: | https://www.home-assistant.io/ |
Keywords: | haos hass homeassistant supervised |
Licenses: | Apache |
Conflicts: | docker-desktop |
Submitter: | rokam |
Maintainer: | rokam (frostwork) |
Last Packager: | rokam |
Votes: | 4 |
Popularity: | 0.000000 |
First Submitted: | 2022-08-05 22:00 (UTC) |
Last Updated: | 2025-01-02 20:28 (UTC) |
Dependencies (14)
- curl (curl-http3-ngtcp2AUR, curl-gitAUR, curl-c-aresAUR)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- docker (rancher-desktop-gitAUR, podman-docker-gitAUR, rancher-desktopAUR, docker-gitAUR, docker-cli-binAUR, podman-docker)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- homeassistant-osagentAUR
- jq (jaq-binAUR, jq-gitAUR)
- systemd (systemd-chromiumosAUR, systemd-fmlAUR, systemd-selinuxAUR, systemd-gitAUR)
- udisks2
- wget (wget-gitAUR, wurlAUR)
- git (git-gitAUR, git-glAUR) (make)
- apparmor (apparmor-gitAUR) (optional) – enhanced security
- cifs-utils (optional) – support for SMB/CIFS mounts
- networkmanager (networkmanager-gitAUR, networkmanager-iwdAUR) (optional) – support for built-in network management
- nfs-utils (optional) – support for NFS mounts
Required by (0)
Sources (1)
fvsc commented on 2025-01-11 10:09 (UTC)
frostwork commented on 2025-01-11 09:45 (UTC)
@fvsc, no it won't help you anything. The "linux system within the docker container" has a problem (nothing is missing in there, it just throws errors). I'd say there's nothing you could do for now, but wait until it is fixed. I truly suggest just keeping an eye on the thread mentioned, or alternatively check for upstream issues. This is really not an Arch related problem! Apart from that, overriding package-management installed packages with manual installs never is a good idea, when you don't know the consequences.
fvsc commented on 2025-01-10 19:40 (UTC)
@frostwork thanks for the info. I wonder if installing python3.12 in /usr/local/bin would be a solution. Any idea?
frostwork commented on 2025-01-10 17:11 (UTC)
@fvsc the error comes from the docker container itself. means the file is not installed in your host system. this is no arch problem "unfortunately". you might want to "+1" in this issue https://community.home-assistant.io/t/every-addon-tells-me-500-internal-server-error/794088/9 or silently lurk what happens there (like I do :))
fvsc commented on 2025-01-10 16:48 (UTC)
@ Stefan T Does not help still: File "/usr/local/lib/python3.12/site-packages/aiohttp/streams.py" looking for pthon3.12
StefanT commented on 2025-01-10 06:07 (UTC)
@fvsc make a clean rebuild your homeassistant-supervised package, this should fix it.
fvsc commented on 2025-01-09 20:15 (UTC)
@frostwork I have the same problem with the logs. 2025-01-09 21:11:01.250 ERROR (MainThread) [supervisor.api] Failed to get supervisor logs using advanced_logs API Traceback (most recent call last): File "/usr/src/supervisor/supervisor/api/init.py", line 403, in get_supervisor_logs return await self._api_host.advanced_logs_handler( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/supervisor/supervisor/api/host.py", line 257, in advanced_logs_handler async for cursor, line in journal_logs_reader(resp, log_formatter): File "/usr/src/supervisor/supervisor/utils/systemd_journal.py", line 101, in journal_logs_reader length_raw = await resp.content.readexactly(8) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/aiohttp/streams.py", line 487, in readexactly raise asyncio.IncompleteReadError(partial, len(partial) + n) asyncio.exceptions.IncompleteReadError: 0 bytes read on a total of 8 expected bytes
python3.12 is needed I have python3.13 installed and not python 3.12
frostwork commented on 2025-01-03 12:38 (UTC)
happy peaceful new year, all!
@rokam thank you for the bump
@gaelic
- yes sure, the system is updated regularly - currently systemd-257.1-1 up and running
- I did not set any specific cmdline parameters at all here (so neither systemd.unified_cgroup_hierarchy=false nor something else instead)
gaelic commented on 2025-01-03 11:06 (UTC) (edited on 2025-01-03 11:12 (UTC) by gaelic)
@frostwork just for clarification:
- you are using the recent systemd?
- which are your kernel parameters? (instead of systemd.unified_cgroup_hierarchy0false ?)
thx, g
StefanT commented on 2025-01-02 19:29 (UTC) (edited on 2025-01-02 19:30 (UTC) by StefanT)
A quick tip for those that also run the openthread border router addon. At the time of writing this addon does not start due to issues open a nat device.
The fix is to downgrade the runc package to 1.1.15 and containerd to 1.7.23. It might be that runc is sufficient (but I have not tried yet).
Pinned Comments
gaelic commented on 2024-06-19 18:07 (UTC) (edited on 2024-06-19 18:48 (UTC) by gaelic)
cgroup v1 is deprecated as of now and my pc is not booting anymore with the required parameter. I am downgrading systemd for the moment, but we need a solution for this problem rather soon. From the systemd changelog (version 256):
Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now considered obsolete and systemd by default will refuse to boot under it. To forcibly reenable cgroup v1 support, SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command line. The meson option 'default-hierarchy=' is also deprecated, i.e. only cgroup v2 ('unified' hierarchy) can be selected as build-time default.
rokam commented on 2022-08-05 22:03 (UTC) (edited on 2022-08-05 22:04 (UTC) by rokam)
You need to add
systemd.unified_cgroup_hierarchy=false
in your kernel parameters.Read more at: https://wiki.archlinux.org/title/Kernel_parameters