Addons: core_ssh addon fails to run after 5.5 update

Created on 3 Jun 2019  路  9Comments  路  Source: home-assistant/addons

Just updated to 5.5 and the core_ssh addon stops after starting.

CONTAINER ID        IMAGE                                      COMMAND                  CREATED             STATUS                       PORTS                                            NAMES
69bdb4fda944        homeassistant/armv7-addon-ssh              "/run.sh"                4 minutes ago       Exited (141) 4 minutes ago                                                    addon_core_ssh

Logs:

# docker logs addon_core_ssh
[21:29:03] INFO: Initializing add-on for use...
[21:29:04] INFO: Setup authorized_keys

I've made no config changes, only updated the addon

bug in progress

Most helpful comment

@ossgeek314 @bjornconnolly Fixed. Should be there now. Sorry about the delay.

All 9 comments

I have the same issue, it works if I don't specify any authorized_keys and instead use a password.

[12:18:17] INFO: Initializing add-on for use...
[12:18:18] INFO: Setup password login
[12:18:19] INFO: Restoring host keys...
[12:18:19] INFO: Starting SSH daemon...
debug1: Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: Bind to port 22 on ::.
Server listening on :: port 22.

Hmmm looking into it right now.

Issue has been addressed, update your SSH add-on to 5.6.

If the update does not appear: Hass.io panel -> Add-on store tab, hit the refresh icon top right. Wait for a second, update shows up 馃憤

I get this when trying to upgrade/install

19-06-03 18:31:20 ERROR (SyncWorker_9) [hassio.docker.interface] Can't install homeassistant/aarch64-addon-ssh:5.6 -> 404 Client Error: Not Found ("manifest for homeassistant/aarch64-addon-ssh:5.6 not found").

Same here (for amd64)

19-06-03 19:23:21 ERROR (SyncWorker_0) [hassio.docker.interface] Can't install homeassistant/amd64-addon-ssh:5.6 -> 404 Client Error: Not Found ("manifest for homeassistant/amd64-addon-ssh:5.6 not found").

@ossgeek314 @bjornconnolly
The build seems to be stuck... We are looking into kicking it back to life... hold on!

@ossgeek314 @bjornconnolly Fixed. Should be there now. Sorry about the delay.

Thanks for the quick fix @frenck

Works perfectly again, thanks @frenck

Was this page helpful?
0 / 5 - 0 ratings

Related issues

joshwapohlmann picture joshwapohlmann  路  8Comments

ludeeus picture ludeeus  路  5Comments

jybi89 picture jybi89  路  10Comments

lordfiSh picture lordfiSh  路  11Comments

d0ugal picture d0ugal  路  14Comments