Supervisor can't install add-ons

I mentioned in the first post that I use Supervised HA installation, this is actual
Supervised Ha runs on Raspbian (I guess last version or close)

Actually, i use like 20 addons and it installs without problem, but this one doesn’t
I googled the error and as I understand this image works on Alpine Linux and there are some problems with getting Alpine Linux image

It shouldn’t matter as the container for the addon will/should have alpine… that’s the point of docker… the container contains and complies with the requirements

Probably you’re right
I just described what I found

So is there any way to install container ?

The addon IS a container. The addon may not be available for your hardware?


i guess this is not matter of hardware

There is some confusion, here, apparently.
The addon is building its own docker image, and this is the step where it’s failing.

OP, I assume the host is a RPI in 32bits.
There is a known issue in this setup as of alpine 3.13. HA currently uses 3.14.

To fix, you have to update libseccomp2 on the RPI host, to a version which is not available in the standard repos. You have to:

# Get signing keys to verify the new packages, otherwise they will not install
$ sudo apt-key adv --keyserver --recv-keys 04EE7237B7D453EC 648ACFD622F3D138

# Add the Buster backport repository to apt sources.list
$ echo 'deb buster-backports main contrib non-free' | sudo tee -a /etc/apt/sources.list.d/debian-backports.list

$ sudo apt update
$ sudo apt install libseccomp2 -t buster-backports

Then retry the addon installation


Thanks, bro! I it works and I’ve installed add on

Hey Chris,

I’m facing the same issue, but running (haos). So I can’t use commands like “apt”. Do you or somebody else have an idea of how I can update libseccomp2 on

Mmm… it shouldn’t happen on HassOS.
Maybe you have a very old version? I don’t actually know how OS upgrades are done on HassOS.

Actually, I’m on the most recent OS version. The OS is on version “core-2021.8.1” and the supervisor is on “supervisor-2021.06.8” using Docker 20.10.6.

I can install add-ons but when I want to install an add-on, that is manually added (concretely “weather station mqtt”) I get following error-log:

Logger: homeassistant.components.hassio
Source: components/hassio/
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 14:57:48 (2 occurrences)
Last logged: 21:12:38

Failed to to call /addons/local_weather_station_mqtt/install - The command '/bin/ash -o pipefail -c apk add --no-cache nodejs-npm' returned a non-zero code: 1

There is a similar issue described in the add-ons git repo that was fixed updating libseccomp2.

That isn’t the OS. If you run ha os it will be 6.2 for the latest version.

Sorry for the misunderstanding - the OS version is 6.2:

  1. What addon is this, specifically
  2. Would have a link to the issue you mention

The addon is: GitHub - jakubonty/weather_station_mqtt

And the correlating issue: Install-Issue · Issue #2 · jakubonty/weather_station_mqtt · GitHub

Indeed, seems to be similar, but libseccomp2 in HassOS is already 2.4.4, apparently, so might be actually be something else.

Do you see the same

WARNING: Ignoring temporary error (try again later)

in the supervisor logs? THAT would mean it’s the same error.

Kind of - I get following Log:

21-08-11 21:37:31 INFO (SyncWorker_4) [supervisor.docker.addon] Starting build for local/armv7-addon-weather_station_mqtt:0.1
21-08-11 21:37:49 ERROR (SyncWorker_4) [supervisor.docker.addon] Can't build local/armv7-addon-weather_station_mqtt:0.1: The command '/bin/ash -o pipefail -c apk add --no-cache nodejs-npm' returned a non-zero code: 1
21-08-11 21:37:49 ERROR (SyncWorker_4) [supervisor.docker.addon] Build log: 
Step 1/18 : ARG BUILD_FROM
Step 2/18 : FROM $BUILD_FROM
 ---> 564b1f71f9e5
Step 3/18 : ENV LANG C.UTF-8
 ---> Using cache
 ---> 42f5d3d4ebd6
Step 4/18 : COPY data/ /
 ---> Using cache
 ---> b6b81c04ad96
Step 5/18 : COPY maserver/* /
 ---> Using cache
 ---> b1c520f3b17d
Step 6/18 : RUN apk add --no-cache nodejs-npm
 ---> Running in d2f6931e0be3
ERROR: unable to select packages:

  nodejs-npm (no such package):
    required by: world[nodejs-npm]
Removing intermediate container d2f6931e0be3

That’s a different issue.
Looks like there is no nodejs-npm package (anymore?)

In the Dockerfile, you have to replace line 10 with

RUN apk add --no-cache nodejs npm

Thank you Chris!! That fixed the issue. I was so focused on libseccomp2 / alpine…

Hi Chris,

Facing the same issue, maybe you could recommend the solution?

Running the latest stable OS in dedicated VM:

Trying to install add-on below:

And getting next errors in the log:
’ 22-01-17 09:21:59 INFO (SyncWorker_2) [supervisor.docker.addon] Starting build for 423ea876/amd64-addon-godaddy_dns:1.0.3
22-01-17 09:22:03 ERROR (SyncWorker_2) [supervisor.docker.addon] Can’t build 423ea876/amd64-addon-godaddy_dns:1.0.3: The command ‘/bin/ash -o pipefail -c apk add --no-cache openssl && curl -s -o /usr/bin/dehydrated “${DEHYDRATED_VERSION}/dehydrated” && chmod a+x /usr/bin/dehydrated’ returned a non-zero code: 1
22-01-17 09:22:03 ERROR (SyncWorker_2) [supervisor.docker.addon] Build log:
Step 1/12 : ARG BUILD_FROM
Step 2/12 : FROM $BUILD_FROM
—> bc9cabb4596e
—> Using cache
—> caffde16250f
Step 4/12 : RUN apk add --no-cache openssl && curl -s -o /usr/bin/dehydrated “${DEHYDRATED_VERSION}/dehydrated” && chmod a+x /usr/bin/dehydrated
—> Running in 1af517d031fe
139785764682568:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914:

WARNING: Ignoring Permission denied

139785764682568:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1914:

WARNING: Ignoring Permission denied

ERROR: unable to select packages:

openssl (no such package):
required by: world[openssl]
Removing intermediate container 1af517d031fe ’

I was pointed by the Michael (developer) the reason is old libseccomp2 library but after reading the thread I feel like it could be something else in my case.


Yep, different.
The date on your machine is wrong (“22-01-17”), and the SSL certificate used by Alpine is “not valid before” 2021, so is refused.

Nevermind, read the date backwards. Definitely a SSL issue, so different though