Exec: fatal: unable to exec bashio: No such file or directory

I was trying to do the " Tutorial: Making your first add-on" (https://developers.home-assistant.io/docs/add-ons/tutorial/) and got this message:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] udev.sh: executing... 
starting version 3.2.8
[12:00:22] INFO: Update udev information
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
exec: fatal: unable to exec bashio
: No such file or directory
[cmd] /run.sh exited 127
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

The intended output is the following:

I didn’t make any alterations to the files given in the tutorial.

I already followed this topic, but it didn’t work.

Any help is appreciated.

Your run.sh script is saved with Dos/Windows (CRLF) line endings. You need to convert this to UNIX-like line breaks (LF).

3 Likes

@breiti thanks for this! I was having the same problem and this was the reason… converted the ‘run.sh’ to UNIX EOL and all worked.

I use Notepad++ on Windows with Samba running on Hassio.

For those who may find this later, to convert to UNIX, do Edit -> EOL Conversion -> UNIX then just resave the ‘run.sh’ to the ‘addon’ folder share.

2 Likes