Not sure what a “true” terminal means nor “buildroot” terminals. There are VTTs, PTTs, terminals that run on top of GUI. Don’t see how any of it would impact docker.
I’m probably using the wrong terminology here. Most of my Linux knowledge is self-taught hobby-related over the years and woefully incomplete.
Homeassistant has multiple installation methods.
If you want the “full features” and also want to keep the option of official support, you need to do one of the following:
-
A “Supervised” installation (Essentially a VERY Specific set of requirements including apparmor/etc, with a specific set of docker containers that are watched over by a “Supervisor” Docker Container that manages parts of the underlying OS and the other docker containers.) that is ONLY supported on vanilla Debian of the current stable version.
-
“The Home Assistant OS” which is essentially a Hypervisor that handles the docker containers mentioned in the Supervised-Style Setup. The OS is very limited. As I understand it, they used “Buildroot” to create an embedded Linux OS that is very restricted. No package managers, nor ways to compile/add them. They appear to actively want to prevent modification of the underlying OS, which is likely the reason for this.
In the end I chose the supervised option because I prefer to have access to the debian OS while still retaining a “supported” status. There are ways to get supervised installations working in Raspian and other flavors, but again that “Unsupported” flag is exactly what I want to avoid.
I looked for a way to adapt the OS Image as well when I first saw your portability app, and tried myself and was unable to do much because of the limits of the terminal. I’m sure there are ways around this, but nothing occurred to me offhand within the constraints. I eventually came across this thread (and a few other similar ones), maybe it will make more sense than I do?
Do you have the MicroSD card make and model? We will test.
The MicroSD Make/Model is a PNY Elite-X. I don’t think this was the fault of the SD card however. This was an issue that affected the 5.18 kernel linked in the Presentation I mentioned in my other post. As soon as I went back to the 5.10 kernel, no more boot issues.
What’s wrong with 3.5mm CVBS out?
The audio is likely an issue with the Alsa settings. I found some information shortly after my original post but haven’t yet had a chance to test it out.