search

OPHoperHPO / hassio-addons

:heavy_plus_sign: Docker add-ons for Hass.io
Apache License 2.0
40 stars 12 forks source link

Addon not starting #8

Closed alanmilinovic closed 2 years ago

alanmilinovic commented 2 years ago

I cannot start addon, tired in Portainer as well and no luck.

This is the error I am getting: s6-overlay-suexec: fatal: can only run as pid 1

MattWestb commented 2 years ago

I think this is some changed is made in HA that is making it not working. https://developers.home-assistant.io/blog/2022/05/12/s6-overlay-base-images/ Also more info https://github.com/just-containers/s6-overlay/blob/master/MOVING-TO-V3.md.

I have one armbian ubuntu 22.04 running on one RK3218 box and i can install docker and HA with patching the installing (so grub is not needed) and its works OK if doing some manual things in docker. In "hassio_audio" container -> edit -> Runtime & Resources and setting CPU 0.25 and the memory to 64 and "update limits" and its only using 25% CPU and not 200%. The back side its needed being done after system is restarted also if only the addon is restarted as HA is deleting the setting and is using 200% CPU.

MattWestb commented 2 years ago

One well working work around found from one bug in HA 2022.6. Edit the container and deleting the /init that is the default for the ENTRYPOINT record and then kicking Override and saving the container and starting it and its fixing the high CUP and then its suspending its self.

[ALSA&PULSEAUDIO FIX][INFO] Module `module-suspend-on-idle` loaded successfully!
jmtatsch commented 2 years ago

Same issue here

timsavory commented 2 years ago

One well working work around found from one bug in HA 2022.6. Edit the container and deleting the /init that is the default for the ENTRYPOINT record and then kicking Override and saving the container and starting it and its fixing the high CUP and then its suspending its self.

[ALSA&PULSEAUDIO FIX][INFO] Module `module-suspend-on-idle` loaded successfully!

When I follow your fix by deleting the /init from entrypoint, select override and the deploy container it restarts in some way it was before. Can you help explain what I am doing wrong? Thanks Tim

MattWestb commented 2 years ago

My changed container config; HAAudiofix-docker only the endpoint and saving the changes and starting the addon from portainer or HA and its not throwing errors and fixing the 200% CPU usage and is backing out then have doing its work..

timsavory commented 2 years ago

My changed container config; HAAudiofix-docker only the endpoint and saving the changes and starting the addon from portainer or HA and its not throwing errors and fixing the 200% CPU usage and is backing out then have doing its work..

Thanks, I will give it a go....

ntguest commented 2 years ago

hi i'm forked and repaired it u can try from this repo https://github.com/ntguest/hassio-audio

OPHoperHPO commented 2 years ago

Hi,

I've added an empty entry point for the docker container by default, as per @MattWestb's info and @ntguest fork changes. I don't have an instance of Home Assistant to test the addon at the moment, so i hope it will works.

MattWestb commented 2 years ago

I have updating HA to 2022.07 and was deleting the old addon and installing the updated version and restarting my NanpPI Neo and the addon is loaded OK and the not working sound is not eating 300% CPU so its looks working OK.

Thanks for fixing the issue HA have doing @OPHoperHPO !!!