Hello,
I am following the custom addon guide to generate a simple addon (https://developers.home-assistant.io/docs/add-ons/tutorial ), but I get always the same error when pressing install button:
ERROR (SyncWorker_2) [supervisor.docker.addon] Invalid build environment, can’t build this add-on!
Is it possible that the guide has been outdated and something is missing?
Thank you so much!!!
koying
(Chris B)
October 12, 2021, 4:39pm
2
Would be easier to tell if the issue is in the doc or between the chair and the display if you’d:
show your addon code
specify your hardware
specify your HA installation method
koying:
Sure!
The HA installation is a hassio Virtual Machine running in VMWare, updated to the latest available stable versions.
The addon code is just the one in the official manual, specifically the one in “Step 1”. It is just a shell with an echo.
Is there any more info that I can share to have any clue?
Thanks!
I see another thread with the same problem, but no answers…
recently i decided to write a custom addon, i followed the initial steps from here , everything working fine up till the step where i want to install the addon once i click on the install button i get the (failed to install the Addon, Unknown Error, see supervisor), when i check the supervisor logs it shows one line related to this error (21-07-22 15:15:00 ERROR (SyncWorker_5) [supervisor.docker.addon] Invalid build environment, can’t build this add-on!)
I am using Home Assistant OS on RP4 ever…
Any clue?
koying
(Chris B)
October 13, 2021, 7:26am
5
I followed steps 1/2/3 on my supervised install on rpi3 and they work.
The only hiccup I had:
The doc says to create the directory directly under /addons, but I had to create it under /addons/local. If you even see your addon, that’s not an issue for you (likely, /addons point to the right place on HassOS)
Copy-paste in VI produced wrong result. I’ll just assume the file you created look exactly like the examples.
Maybe / Probably something specific to HassOS (that I cannot test).
My bad…
the file “Dockerfile” in my case was “dockerfile”.
Thank you so much.