[BUG] Name has no usable address #139
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
This one is weird, but i'm noticing more and more people seeing it.
In some environments (mine is kubernetes), in the linuxserver homeassistant container, ping/python are unable to resolve addresses... while curl is able to resolve addresses.
Do a google search for "Name has no usable address", and you'll find a bunch of misc HA integrations complaining about this error. it's extremely vague, and presents itself oddly.
Expected Behavior
No response
Steps To Reproduce
# curl google.com
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="http://www.google.com/">here</A>.
</BODY></HTML>
# ping google.com
ping: google.com: Name has no usable address
# python
Python 3.13.7 (main, Aug 14 2025, 19:18:09) [GCC 14.2.0] on linux
.
.
>>> import socket; print(socket.getaddrinfo('google.com', 80))
socket.gaierror: [Errno -5] Name has no usable address
Environment
Kubernetes 1.34
ARM64
Flannel CNI
CoreDNS
HA deployed as a deploymentCPU architecture
arm64
Docker creation
apiVersion: apps/v1
kind: Deployment
metadata:
name: homeassistant
namespace: homeassistant
labels:
app: homeassistant
spec:
replicas: 1
selector:
matchLabels:
app: homeassistant
template:
metadata:
labels:
app: homeassistant
spec:
containers:
- name: homeassistant
image: lscr.io/linuxserver/homeassistant:latest
securityContext:
privileged: true
allowPrivilegeEscalation: true
capabilities:
add: ["NET_ADMIN", "SYS_TIME"]
drop: ["ALL"]
ports:
- containerPort: 8123
volumeMounts:
- name: config
mountPath: /config
volumes:
- name: config
hostPath:
path: /var/lib/containers/pv/ha-config
type: DirectoryContainer logs
$ kubectl -n homeassistant logs homeassistant-696dcfc58b-vk6nh
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 911
User GID: 911
───────────────────────────────────────
Linuxserver.io version: 2025.10.4-ls154
Build-date: 2025-10-29T02:15:24+00:00
───────────────────────────────────────
**** New container detected, fixing python package permissions. This may take a while. ****
Setting permissions
[custom-init] No custom files found, skipping...
Adding cap_net_admin and cap_net_raw to python binary for bt access
2025-10-29 15:12:45.385 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration rivian which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
Connection to localhost (::1) 8123 port [tcp/*] succeeded!
[ls.io-init] done.
2025-10-29 15:12:49.598 WARNING (SyncWorker_2) [homeassistant.components.openevse.sensor] Could not update status for Charging Status
2025-10-29 15:13:19.620 WARNING (SyncWorker_2) [homeassistant.components.openevse.sensor] Could not update status for Charging Status
2025-10-29 15:13:49.618 WARNING (SyncWorker_3) [homeassistant.components.openevse.sensor] Could not update status for Charging Status
2025-10-29 15:14:19.623 WARNING (SyncWorker_0) [homeassistant.components.openevse.sensor] Could not update status for Charging Status