Skip to content

Conversation

@clairtonluz
Copy link

This PR updates the base image from node:14-slim to node:18-slim in order to fix the installation/build failure.

The issue with the current base image (node:14-slim) is that it relies on Debian Buster, whose repositories are no longer available or maintained. As a result, apt-get update fails, breaking the Docker build process.

By switching to node:18-slim, which uses a newer and supported version of Debian, the build process succeeds again. Additionally, python was replaced with python3 to ensure compatibility with modern Debian packages.

@slavo74
Copy link

slavo74 commented Jul 16, 2025

How do I fix this? Please follow the steps or change the add-ons link. Thanks!
I have this error!
Docker build failed for f4f71350/aarch64-addon-ewelink_smart_home_slug:1.4.3 (exit code 1). Build output: #0 building with "default" instance using docker driver #1 [internal] load build definition from Dockerfile #1 transferring dockerfile: 403B done #1 DONE 0.1s #2 [internal] load metadata for docker.io/library/node:14-slim #2 DONE 0.2s #3 [internal] load .dockerignore #3 transferring context: 2B done #3 DONE 0.1s #4 [1/7] FROM docker.io/library/node:14-slim@sha256:198142146b4c47193348f6415da769bdb5035c16fcab051c38c256a6b48f2e1c #4 CACHED #5 [internal] load build context #5 transferring context: 4.23MB 0.1s done #5 DONE 0.2s #6 [2/7] RUN apt-get update && apt-get install -y python build-essential #6 0.371 Ign:1 http://deb.debian.org/debian buster InRelease #6 0.378 Ign:2 http://deb.debian.org/debian-security buster/updates InRelease #6 0.384 Ign:3 http://deb.debian.org/debian buster-updates InRelease #6 0.391 Err:4 http://deb.debian.org/debian buster Release #6 0.391 404 Not Found [IP: 199.232.18.132 80] #6 0.398 Err:5 http://deb.debian.org/debian-security buster/updates Release #6 0.398 404 Not Found [IP: 199.232.18.132 80] #6 0.404 Err:6 http://deb.debian.org/debian buster-updates Release #6 0.404 404 Not Found [IP: 199.232.18.132 80] #6 0.408 Reading package lists... #6 0.418 E: The repository 'http://deb.debian.org/debian buster Release' does not have a Release file. #6 0.418 E: The repository 'http://deb.debian.org/debian-security buster/updates Release' does not have a Release file. #6 0.418 E: The repository 'http://deb.debian.org/debian buster-updates Release' does not have a Release file. #6 ERROR: process "/bin/sh -c apt-get update && apt-get install -y python build-essential" did not complete successfully: exit code: 100 ------ > [2/7] RUN apt-get update && apt-get install -y python build-essential: 0.391 Err:4 http://deb.debian.org/debian buster Release 0.391 404 Not Found [IP: 199.232.18.132 80] 0.398 Err:5 http://deb.debian.org/debian-security buster/updates Release 0.398 404 Not Found [IP: 199.232.18.132 80] 0.404 Err:6 http://deb.debian.org/debian buster-updates Release 0.404 404 Not Found [IP: 199.232.18.132 80] 0.408 Reading package lists... 0.418 E: The repository 'http://deb.debian.org/debian buster Release' does not have a Release file. 0.418 E: The repository 'http://deb.debian.org/debian-security buster/updates Release' does not have a Release file. 0.418 E: The repository 'http://deb.debian.org/debian buster-updates Release' does not have a Release file. ------ �[33m1 warning found (use docker --debug to expand): �[0m - JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals (line 13) Dockerfile:6 -------------------- 4 | FROM node:14-slim 5 | ENV CK_API_ENV=prod 6 | >>> RUN apt-get update && apt-get install -y python build-essential 7 | RUN mkdir -p /workspace/node_modules 8 | COPY ["./dist", "./package.json", "/workspace/"] -------------------- ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get install -y python build-essential" did not complete successfully: exit code: 100

@clairtonluz
Copy link
Author

clairtonluz commented Jul 18, 2025

@slavo74 if you want use my repository while this PR is pedding to be accepted, you can follow the official documentation in this link:
https://ewelink.cc/ewelink-works-with-home-assistant/

but when arrive in the session installation instead of you use https://github.com/CoolKit-Technologies/ha-addon you can use my repository https://github.com/clairtonluz/ha-addon, so you can install with success.

image

when the team of CoolKit Technologies accept my PR and fix this problema you can remove my repo e go back to the offical repository.

@RandMental
Copy link

https://github.com/clairtonluz/ha-addon does not work - gives unknown error during installation on RPI OS HA

@clairtonluz
Copy link
Author

@RandMental which error was throw to you, here in my raspberry PI I was using and it`s working.

@Dachaz
Copy link

Dachaz commented Jul 31, 2025

Hi, @clairtonluz — on Home Assistant Green, your branch builds, but it's not exposing Options where the long-lasting token is supposed to be entered (only Network section is visible). Is this expected?

Screenshot 2025-07-31 at 11 45 46

@clairtonluz
Copy link
Author

Home Assistant Green

Hi, @Dachaz , This is ok, after you start add-ons you can open web interface where you can login using you app, I only update base image version as you can see on PR. This add-ons keeping working as before.

You only need

1 - Install add-on
2 - Start add-on
3 - Click on button to open web interface
4 - Login using you ewelink account
5 - Done, you are integrated with you ewelink account.

@anlie3000
Copy link

Hi @clairtonluz,
I get the following error message when I try to add the repository in Home Assistant (VM):

Cmd('git') failed due to: exit code(128) cmdline: git clone -v --recursive --depth=1 --shallow-submodules -- https://github.com/clairtonluz/ha-addon /data/addons/git/48c7eec6 stderr: 'Cloning into '/data/addons/git/48c7eec6'... fatal: unable to access 'https://github.com/clairtonluz/ha-addon /': URL rejected: Malformed input to a URL function '

@eparge eparge mentioned this pull request Aug 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants