You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to run a Home Assistant Supervised installation inside of a container, but it have some serious dependencies on host, including Systemd and Docker.
So I though: Sysbox to the rescue!
And, I stumbled upon one issue. During the installation of homeassistant-supervised.deb it tries to write to /proc/sys/kernel/dmesg_restrict which fails with permission denied.
Some claims that --privileged seems to work around this issue, but I think it does not work when using sysbox-run, like --runtime=sysbox-runc --privileged.
I'm trying to run a Home Assistant Supervised installation inside of a container, but it have some serious dependencies on host, including Systemd and Docker.
So I though: Sysbox to the rescue!
And, I stumbled upon one issue. During the installation of
homeassistant-supervised.deb
it tries to write to/proc/sys/kernel/dmesg_restrict
which fails with permission denied.https://github.com/home-assistant/supervised-installer/blob/a3d1502f5159170ea5c01c47c9c08121dd4d0328/homeassistant-supervised/DEBIAN/preinst#L20
Some claims that
--privileged
seems to work around this issue, but I think it does not work when usingsysbox-run
, like--runtime=sysbox-runc --privileged
.https://stackoverflow.com/questions/41171349/why-is-a-shell-within-a-docker-container-showing-dmesg-content-from-the-host
It would be really nice if Sysbox could help in this situation. :)
The text was updated successfully, but these errors were encountered: