Not sure if this is the right place to ask for help, if not please let me know where to post. I’m attempting to do some add-on work and trying to leverage the devcontainer for add-ons following the instructions here: add-on testing and I’m having some trouble with the resultant container. While home assistant starts I get a bunch of major subsystems errors (systemd, systemd-journal, operating system, network manager, etc…). The add-on starts but doesn’t work and doesn’t log any things (probably due to the systemd-journal issues. I’m doing this on a mac with Sequoia 15.x. Any ideas what I might be missing?
2 Likes
You are not the only one: Discord
did anybody found a solution yet?
@danieldotnl how to access the discord?
I got it at least to start with running:
mount --make-shared /
in the devcontainer.
But now I’m stuck on the onboarding screen of homeassistant.
But it looks like the websocket connection is working and also no errors in the js console:
Wow I have the same issues. If there is a solution I would be happy to hear it!
A possible solution is to change to the lastest image. You can see an example in this commit:
Update eos to the latest version by paule96 · Pull Request #19 · Duetting/ha_eos_addon
But be aware starting home assistant like that takes some time (10 to 15mins)
Ignore all weird errors while the first 10 to 15min ^^
This seems to have got even worse - it is now not possible to install addons in the devcontainer as the system is detected as unhealthy. At least that is what I have experienced. Is this killing addon development for other people too?