-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Alpine linux 3.21.1 missing Entrust root certificates #121
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Yep we're aware of this. Unfortunately need to wait for it to be fixed upstream then our containers will pickup the fix. |
That fix isn't in the 3.21 release that the current container is based off of. I verified the fix by manually installing the update in a running container. Like @j0nnymoe said, we need to wait for alpine to release a version that has that fix installed. |
Looks like they specifically targeted the ca-certificate package version, with the patch to add the EnTrust CA certs back in: Last version I had working was HA 2025.1.0. That version still had: 20241010-r0 , but it's also Alpine Linux 3.21 Couldn't you just update the package_versions.txt to the -r1 one? |
No, thats not how it works |
package_versions is an output not an input. The ca-certificates package is sourced from the base image, which is what needs updating before another HA build is triggered. |
Oh looks like the bot picked up the changes and pulled in Alpine Linux 3.21.2 for the base image just a few minutes ago. |
I've trigged a Home Assistant build as its next scheduled check isn't until Monday |
Hey, is it possible, that this new build is not working correctly? Here is what i get with the new build: failed to set capabilities on file 'usr/local/bin/python3.13,bak' : no such file or directory Image: Linuxserver.io version:- 2025.1.2-ls66 Build-date:- 2025-01-10T20:32:10+00:00 Running on Docker on Raspberry Pi 5 Error since the container is running with the new build. With Linuxserver.io version:- 2025.1.2-ls65 Build-date:- 2025-01-09T23:58:30+00:00 the container is running fine |
Smoke test look fine https://ci-tests.linuxserver.io/linuxserver/homeassistant/2025.1.2-ls66/index.html |
It's also working fine yesterday afternoon for me right after @thespad triggered the new build. |
Thank you for your feedback, I will have a look, maybe the issue is on my side then. Will have a look. |
Is there an existing issue for this?
Current Behavior
The current 3.21 build of alpine is missing some root certificates. This causes any kind of https request to one of these services to fail.
eg. home-assistant/core#135233
More info here: https://sslmate.com/blog/post/entrust_distrust_more_disruptive_than_intended
Expected Behavior
No response
Steps To Reproduce
$ podman run --rm -it ghcr.io/linuxserver/homeassistant curl -vvI https://maps.geogratis.gc.ca
Will fail with ssl errors
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: